|
|
|
|
|
|
by oconnor663
209 days ago
|
|
|
> They did this by not breaking the universe in these major updates I don't think the amount of breakage per se was the problem with Python 3. I think the problem was that for a long time (until u"" strings in 3.3? four years after 3.0?) there was ~no way for a library to support both 2 and 3 in a single codebase. That meant that each project had to either maintain a fork, or do a "flag day" migration, which in practice meant you couldn't migrate until all your dependencies were migrated. Big mistake in retrospect. |
|
|
The lack of u"" is just another manifestation of the complete breakage they wrought upon Python's string handling, isn't it?
It was closer to a decade (3.7) till they'd put enough of the bits they'd ripped out back in for Py3 to be suitable for the things I used Py2 for.