GIL Become Optional in Python 3.13

Re:GIL Become Optional in Python 3.13 by CJefferson on Monday August 12, 2024 @03:58PM (#41228641)

My problem is some libraries which never transitioned from 2 to 3. I don't want to try to convert them, particularly as they involve Unicode which is one of the hardest bits to get right in my experience.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by skeledrew on Monday August 12, 2024 @10:08PM (#41231468)

Improved unicode (string vs byte separation) handling was exactly one of the larger reasons for the breaking change to 3.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by CJefferson on Tuesday August 13, 2024 @04:54AM (#41233601)

You are right that unicode is much better in 3, but in my experience this is a pain point mapping programs 2 -> 3, because often programs seem to work fine until there is some exciting unicode, or malformed characters, in the input, then they crash when they used to just rumble on.

[ Parent | on HN ]

Re:GIL Become Optional in Python 3.13 by skeledrew on Wednesday August 14, 2024 @12:47AM (#41242650)

That sounds about right. Fail fast and loud so things have to be fixed, rather than continue silently and likely corrupt data.

[ Parent | on HN ]