tauthon

I'm not sure why python is called out as being better here. The PSF came calling for a rename pretty quickly when tauthon (https://github.com/naftaliharris/tauthon) was launched as it was initially describing itself as python 2.8

Python 3 is a disaster for many other reasons, UTF-8 bugs is just one of them. So far I'm sticking with Tauthon[1] which seems to be the best of both worlds. 1.: https://github.com/naftaliharris/tauthon

> If someone wanted other than the core Python team wants to step up and maintain Python 2, they are free to do so, it's open source. Only if they name it something completely different from python or py-anything. Guido refuses to allow anyone to just step in to maintain py2. Tauthon is a project that aims to keep compatability with py2 while adding whatever features of py3 that won't break py2 and to have a maintained py2. https://github.com/naftaliharris/tauthon

https://github.com/naftaliharris/tauthon/issues/47 (I've definitely seem other cases, but I can't find them). Here is someone wanting to call something 'py28', and Guido replies "OK, bring in the lawyers".

Sorry, I shouldn't assume people know the same things I know. I know this has come up at least three times I've seen, but I'm having trouble finding them all. Here's one: https://github.com/naftaliharris/tauthon/issues/47 In this case there was plans to call something py28, to which Guido replied "OK, bring in the lawyers".

Sad to see them forging ahead on their plans to drop Python 2, and it would have been nice of them to point out that other volunteers will provide security fixes for Python 2 compatible runtimes. I've switched to Tauthon [1] for over a year now and have been quite pleased. Consider the switch yourself rather than rewriting your code. [1] https://github.com/naftaliharris/tauthon

There is Tauthon[1] which backports Python 3 features to 2 and seems to do the "actual work". It has been around a while. It was also posted in this thread below by the current maintainer of the project but for some reason that comment was downvoted to [dead]. By reading a bit around about it, i do get the impression that the Tauthon developers face a bit of hostility from the Python community, so i'm not sure how viable it'll be in the long term. I suppose it depends on how stubborn the Tauthon developers are :-P [1] https://github.com/naftaliharris/tauthon

We are volunteers who make and take care of a Python2 fork with backwards-compatible Python3 features. That means we will keep on improving it without breaking your code base or forcing you to hire the language creator and spend more than 3 years porting your code to Python3, with no actual business benefits. https://github.com/naftaliharris/tauthon/

>> What’s to stop someone else from backporting security fixes as needed ad infinitum? >Who? I haven’t heard anyone express a willingness to take up that mantle. Tauthon [0] kind of fits the bill here. It's a fork of 2.7 with some backported features from the 3 branch, so they're in a position to backport security fixes as well. How well that arrangement holds up once the PSF officially drops 2 remains to be seen, but if anybody is in a position to keep providing support it's probably them. [0] https://github.com/naftaliharris/tauthon

I do not understand the ramifications, but how come nobody ever answers "Tauthon" to this discussions? https://github.com/naftaliharris/tauthon Background: https://www.naftaliharris.com/blog/why-making-python-2.8/