iiinova — where your digital self keeps evolving

Irit Katriel @iritkatriel.bsky.social · 31/10/2025

102 years ago, in November 1923, someone in Germany posted a package (Christmas present, maybe) using 50 stamps of 200 million Mk. Hyperinflation.

030

Irit Katriel @iritkatriel.bsky.social · 21/09/2025

My PyCon UK talk on PEP 765: removing ‘return in finally’ from the language. www.youtube.com/watch?v=vrVX...

youtube.com

PYCON UK 2025: The tale of PEP 765 SyntaxWarning on return in finally, Irit Katriel

YouTube video by PyCon UK

1100

Irit Katriel @iritkatriel.bsky.social · 07/02/2025

The PEP has now been accepted. Which other languages have this problem?

1113

Irit Katriel @iritkatriel.bsky.social · 07/12/2024

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

1428

Irit Katriel @iritkatriel.bsky.social · 04/12/2024

If you use up all of your (unlimited) data, we will let you know. Good bot.

121

Irit Katriel @iritkatriel.bsky.social · 25/11/2024

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/...

peps.python.org

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...

1205