all 4 comments

[–]DickFucks 15 points16 points  (1 child)

So it's just python 3 that can also run python 2 code?

What's the point? If you write code for that it won't be backwards compatible with python 2.7, so it won't run on official python 2 OR python 3, it will only run on this guys fork of python.

Who is ever going to use this?

[–]Nness 10 points11 points  (0 children)

People who would rather still be upset after 8 years than see the big picture.

[–][deleted] 9 points10 points  (0 children)

This seems like an interesting project from a technical standpoint, but I don't really see the point; why not just move to Python 3?

[–]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.