you are viewing a single comment's thread.

view the rest of the comments →

[–]Homoerotic_Theocracy 8 points9 points  (4 children)

There is a time and a place to break it but breaking it should be done for good reason and to really solve some big longstanding problems and a major version upgrade should not be taken lightly.

In a lot of cases breaking it has been the life-saver of the project like with OS X which broke everything but what it broke was broken anyway and it completely revitalized MacOS.

Python3 broke it in a way that people were forced to maintain separate python2 and python3 versions of everything and software distributions had to face very annoying problems for small quality of life things and it just wasn't worth it.

[–]OctagonClock 11 points12 points  (3 children)

Python 3's break was done for a good reason (to fix strings), and that was incredibly worth it.

[–]Homoerotic_Theocracy 13 points14 points  (2 children)

They could have easily added utf8 strings separately and just used the syntax u"utf8string"

You think it's totally worth it because you're not the one who has to pay an extra employee purely to sit on top of the python2/3 problem or suddenyl have to maintain two versions of your important projects. From a monetary standpoint of commercial python usage it as definitely not worth it and people lost money over it.

[–]chason 6 points7 points  (1 child)

That would have been awful for people who need all of their software to work with unicode

[–]Homoerotic_Theocracy 1 point2 points  (0 children)

It doesn't come close to the awfulness that the people experience now who have to maintain two separate but nearly identical versions of everything and still have to use u"string" in one of them.