On 10 December 2016 at 13:49, M.-A. Lemburg <m...@egenix.com> wrote: [...]
> Regardless of the name, it'll be interesting to see whether > there's demand for such a fork. Without a website, binaries > to download, documentation, etc. it's still in the very early > stages. > IMHO, whether or not there is demand for this release should be irrelevant. Caving in to Python 2.8 demand is trading off some short term gains (adding some Python 3 features to code bases locked into Python 2), in detriment of a big long-term risk, which is that the Python language permanently forks into two versions: Python 2 and Python 3. Right now we have a solid expectation that eventually Python 2 is going to be legacy and most code bases will convert to Python 3. If we somehow endorse Python 2.8, many developers will be tempted to just stick with Python 2 forever. This would be very very bad for the future of the language as whole.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
