Python 3.13, what didn't make the headlines (www.bitecode.dev)

submitted 4 weeks ago by norambna@programming.dev to c/python@programming.dev

11 comments fedilink hide all child comments

via https://framapiaf.org/@bitecode/113368174297795284

top 11 comments

sorted by: hot top controversial new old

[-] vahtos@programming.dev 14 points 4 weeks ago

What a refreshingly information dense blog without the typical annoying web page behaviors (consent pop-ups, join our mailing list, etc). Thanks for sharing.

[-] Midnitte@beehaw.org 9 points 4 weeks ago

I guess they need some tips to up their game

[-] rutrum@lm.paradisus.day 7 points 3 weeks ago

Thats a wonderful article. Thank you for sharing

[-] xigoi@lemmy.sdf.org 1 points 4 weeks ago

It did ask for my e-mail.

[-] tunetardis@lemmy.ca 8 points 4 weeks ago

I've been playing around with the disabled GIL build and though I use threads fairly extensively in my projects, it's been smooth sailing so far. I feel like my GUI scripts might be a bit more responsive now? (I tend to farm out user events to dedicated threads, so this is entirely possible.)

But overall, everything is stable and awesome! I'm so excited! This has been a long time coming for Python.

[-] solrize@lemmy.world 0 points 4 weeks ago

Explain?

[-] gigachad@sh.itjust.works 10 points 4 weeks ago

Wdym? It's a text about the lesser known features and changes in Python 3.13.

[-] solrize@lemmy.world 2 points 4 weeks ago

There's some confusing code there. What does it do?

[-] sugar_in_your_tea@sh.itjust.works 5 points 4 weeks ago* (last edited 4 weeks ago)

You mean the code under "The annotation change nobody asked for"? That's not intended to do anything, it's supposed to just be valid Python code as an annotation. Basically, they're trying to break the type hinting system.