iritkatriel

mcc, 7 months ago to random

A thing I feel writing Python is that visually decoding exceptions (the primary form code errors come in) is too much cognitive work, and there are things the interpreter could do to help.

Consider this (long, verbose!) extension trace. Only the pink circled part is important. The interpreter can't know that; that's AI-complete. But the interpreter could know which lines are "my code" and which are "library code", and color-code the background. Then I could just scan for the final "Me" line.

iritkatriel, 7 months ago to random

At the last Python Language Summit in April, after three back-to-back sessions on the C API, we agreed that our discussions about the future of the C API are lacking a shared understanding of its current state, its strengths and weaknesses.

We decided to work towards a document summarising a community consensus on that, and have now put together the draft of PEP 733.

https://peps.python.org/pep-0733/

iritkatriel, 10 months ago to random

Error Handling: From Charles Babbage to Python 3.11

This talk introduces the new error handling features of Python 3.11, while placing them within their historical perspective.
https://www.youtube.com/watch?v=rKBKHVvXuUI&t=559s