Szorc: Mercurial's Journey to and Reflections on Python 3

Posted Jan 15, 2020 19:43 UTC (Wed) by nim-nim (subscriber, #34454)
In reply to: Szorc: Mercurial's Journey to and Reflections on Python 3 by excors
Parent article: Szorc: Mercurial's Journey to and Reflections on Python 3

I guess that just shows that the Python team was right to decide that transitioning to unicode required forcing devs to use unicode. And that, despite all the grief they got about it over years, (and continue to get in this article), they didn’t go far enough.

People still managed to find loopholes and other ways to sabotage the migration.

Szorc: Mercurial's Journey to and Reflections on Python 3

Posted Jan 15, 2020 19:56 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

> People still managed to find loopholes and other ways to sabotage the migration.
Perhaps Python should have also required rewriting all the code backwards? It would have been just as useful!

Szorc: Mercurial's Journey to and Reflections on Python 3

Posted Jan 16, 2020 8:44 UTC (Thu) by nim-nim (subscriber, #34454) [Link]

Yes, right, say the people who are quite happy to use filesystems with working filenames, but see no reason to make the effort to generate working filenames themselves.

That’s called the tragedy of the commons.