GIL Become Optional in Python 3.13

Re:GIL Become Optional in Python 3.13 by KaiserPro on Monday August 12, 2024 @05:51AM (#41222798)

I'm still not clear on what the real benifit of python3 over 2 was.

I use python3 now by default, as it has fstrings, and probably some iteration things that I now rely on, and is faster for a lot of things.

But for the longest time the only difference that I bumped into was that print isnt a keyword anymore, but assert still is.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by robertlagrant on Monday August 12, 2024 @06:38AM (#41223012)

The main breaking change was Unicode for strings, which is what caused all the pain as lots of code was written to assume ASCII strings.

But it's good that it's Unicode.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by KaiserPro on Monday August 12, 2024 @08:07AM (#41223497)

Ahhh yes, that brings back memories. This also meant that stuff coming from things like UARTs and sockets were binary, rather than strings in python3.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by Izkata on Monday August 12, 2024 @12:09PM (#41226064)

For anyone who doesn't remember: A python3 design decision they went partially back on meant it was easier to go from 2.7 to 3.3 than it was to go from 2.7 to 3.0

(I think it was 3.3 when they compromised, maybe 3.4?)

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by robertlagrant on Wednesday August 14, 2024 @03:02AM (#41243304)

3.3 - they reallowed unicode literals.

[ Parent | on HN ]