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.