Re:Mercurial’s journey to and reflections on Python 3
by int_19h on Tuesday January 14, 2020 @03:08AM
(#22042800)
It would still be a mess any time you have to deal with byte strings that aren't UTF-8. The problem is with the implicit conversion itself - it shouldn't happen, because there's no way to properly guess the encoding. But there was no way to get rid of it without breaking things.
Re:Mercurial’s journey to and reflections on Python 3
by otabdeveloper4 on Tuesday January 14, 2020 @04:43AM
(#22043272)
> But there was no way to get rid of it without breaking things.
Even such a breaking change would be a molehill compared to the mountain of breaking changes in Python 3.
Point is, they had one job, and they failed.
Re:Mercurial’s journey to and reflections on Python 3
by int_19h on Tuesday January 14, 2020 @12:26PM
(#22046975)
That change was at the heart of the breaking changes around strings in Python 3. If the conversions remained implicit, most people would probably have never even noticed that string literals default to Unicode, or that some library functions now require Unicode strings.
They could have just changed the default encoding to utf8. (For those too lazy to configure their Python properly.)
There, problem solved - and no need for a breaking Python 3.