News for hackers. Stuff that matters.
Re:Mercurial’s journey to and reflections on Python 3 by hackbinary on Monday January 13, 2020 @02:09PM (#22037507)
I disagree. If someone else wants to continue to develop Python 2 outside the Python foundation and formalised development community, then that is their prerogative, but Python has the right to decide what is and is not Python.

Dilution of what is commonly accepted to be Python would not be a good thing, and would further add to confusion.

I know that platform upgrades are painful, but we need to move with the times or we'll all be mired in technical debt and old technology.

Re:Mercurial’s journey to and reflections on Python 3 by takeda on Monday January 13, 2020 @05:07PM (#22039249)
Yes, them keeping Python 2 alive for 10 years where Python 3 was developed caused a lot of issues, it would be extremely short sighted to allow third (incompatible) python into the mix.
Re:Mercurial’s journey to and reflections on Python 3 by hsivonen on Tuesday January 14, 2020 @01:52AM (#22042469)
> it would be extremely short sighted to allow third (incompatible) python into the mix

The whole point of Tauthon is that it is compatible with Python 2 (in the direction that old programs work).