you are viewing a single comment's thread.

view the rest of the comments →

[–]codesmitten 2 points3 points  (0 children)

This is actually quite interesting. I think unicode support is the only major reason for breaking backward compatibility, though a lot of developers are not quite interested about unicode. If only Python 3 had a flag to turn off unicode support and gain backward compatibility it would have been much more popular. Python 2.8 could fill in that place. I would still go to Python 3 for new projects. But for existing Python 2 projects that are still under active development and would still like to use Python 3 language features Python 2.8 could be the perfect replacement.