Irit Katriel
iritkatriel.bsky.social
Irit Katriel
@iritkatriel.bsky.social
CPython Core Dev. Views are my own.
102 years ago, in November 1923, someone in Germany posted a package (Christmas present, maybe) using 50 stamps of 200 million Mk. Hyperinflation.
October 31, 2025 at 10:48 AM
My PyCon UK talk on PEP 765: removing ‘return in finally’ from the language.

www.youtube.com/watch?v=vrVX...
PYCON UK 2025: The tale of PEP 765 SyntaxWarning on return in finally, Irit Katriel
YouTube video by PyCon UK
www.youtube.com
September 21, 2025 at 8:07 AM
Tough choice..
May 27, 2025 at 9:25 PM
The PEP has now been accepted.

Which other languages have this problem?
February 7, 2025 at 12:01 AM
LWN published a good summary of the discussion so far:
lwn.net/Articles/100...

@lwndotnet.bsky.social
December 29, 2024 at 7:28 PM
I'm working on CPython's internals documentation, collecting it all into one place, organising, updating and enhancing to fill in missing topics.

It's taking shape, but there are still gaps to fill. Contributions are welcome.

github.com/python/cpyth...
github.com
December 7, 2024 at 10:33 PM
If you use up all of your (unlimited) data, we will let you know.

Good bot.
December 4, 2024 at 4:47 PM
I conducted an analysis of return-in-finally in real world Python code. Just don't do it.

TL;DR:
- it is not used often
- when it is used, it's usually used incorrectly
- code authors find it easy to fix

Draft PEP: peps.python.org/pep-0765/

Full report: github.com/iritkatriel/...
PEP 765 – Disallow return/break/continue that exit a finally block | peps.python.org
This PEP proposes to withdraw support for return, break and continue statements that break out of a finally block. This was proposed in the past by PEP 601. The current PEP is based on empirical evide...
peps.python.org
November 25, 2024 at 3:40 PM