Why I'm Making Python 2.8
As others have said, maybe this project fixes some actual problems and backports some features from 3, but this isn&#x27;t &quot;Python&quot;. Beyond the fact that Python is a trademark of the Python Software Foundation, Python is more than the language, it&#x27;s the community and the tools (as with every programming language). So while there are some vocal people that really dislike Python 3 (either in part or wholly), my understanding is that with the planned phase out of Python 2 and Python 2 only receiving bug fixes at this point, much of the industry is transitioning to Python 3 (either currently doing so or planning to) and so it seems relatively fruitless to attempt to build upon Python 2. I personally think the effort put into this would be much better spent making tooling around Python 2 to 3 transformations.<p>I also think it&#x27;s pretty irresponsible of the author to call this Python 2.8, because it may cause confusion to developers unfamiliar with the history and come from a tutorial that is still in Python 2 (it does show up on the first page of Google for me). It&#x27;s also especially irresponsible and hubristic to attempt to make a language that is seemingly compatible with both Python 2 and 3, because 1) I trust that if it was possible Guido and the other developers would have made it, and 2) it can cause significant confusion when code doesn&#x27;t work when it hits an edge case, and then the whole tooling around it can&#x27;t be guaranteed to work. The last thing I&#x27;d want in my programming language is unaccounted for ambiguity.