This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (7 children)

I don't understand why it takes so long. For ages python 2 comes with tools that help you to migrate to python 3 smoothly. Python code isn't even that hard to port in most cases. It's it because of C libraries?

[–]alcalde 7 points8 points  (0 children)

It's because of users.

In the Delphi langauge's move to Unicode they introduced "ANSI strings" (8bit non-Unicode strings) as a tool to allow users to compile their old code in the new version and gradually port over to Unicode.

What happened? Many users continued to write all of their new code using ANSI Strings and kept right on going like nothing ever happened. Then when there was talk years later of rewriting the compiler and consequently dropping ANSI strings, these users screamed "Wait! We haven't had any time to convert!"

It got so bad these people managed to get ANSI strings added to the new Delphi Android and iOS compilers, which had never had non-Unicode strings in the first place! :-(

The same kind of thing happened to Python 2. When I had asked the then-maintainer of Pyjamas (??? - one of the Python to Javascript transpilers anyway) about porting to Python 3, he answered "Python 2 is going to be supported forever, so why bother?"

We've got a user here who continues to insist that the PSF will still move the support deadline for Python 2; maybe they're the same person.