News for hackers. Stuff that matters.
Re:Sunsetting Python 2 by wongarsu on Monday September 09, 2019 @04:47AM (#20916301)
Continuing a fork under the original name would be confusing to everyone and bad manners, aside from infringing the trademark. But nobody is stopping people from organising around a fork called "Omphalos - a Python 2 fork" or whatever
Re:Sunsetting Python 2 by toyg on Monday September 09, 2019 @06:03AM (#20916727)
Somebody has done just that already, it’s easily googleable. Nobody really cares though - why would you purposefully tie yourself to an objectively-inferior featureset, full of problems that have already been solved in py3? Because you can’t bear the use of parentheses for print, really?
Re:Sunsetting Python 2 by jsjohnst on Monday September 09, 2019 @07:09AM (#20917041)
> Because you can’t bear the use of parentheses for print, really?

While I generally share your POV, it doesn’t do justice to the situation to trivialize the upgrade like that. Anyone with C based dependencies will have a rougher time (but not that “rough”) due to ABI changes. The harder userland change is string handling anyway (which isn’t that hard either), not parens on print.

Re:Sunsetting Python 2 by toyg on Monday September 09, 2019 @07:49AM (#20917245)
You are right. I'm probably still shellshocked by the initial wave of complaints, so many years ago...
Re:Sunsetting Python 2 by Drdrdrq on Tuesday September 10, 2019 @01:20AM (#20925235)
...and those parenthesis are annoying as hell. :)
Re:Sunsetting Python 2 by zajio1am on Monday September 09, 2019 @08:19AM (#20917414)
It would not be fork when the original project (Python 2) is no longer developed. There are many cases of cooperative maintainership handover without name change and nobody cares.

I understand using trademark as an advantage in cases of a hostile fork, but if the original maintainer no longer plan to do any bugfixing then it seems like a dick move.

Re:Sunsetting Python 2 by wongarsu on Monday September 09, 2019 @08:29AM (#20917472)
The original project (Python) is still developed however. If a handoff to some other team occurs and the new maintainers do a bad job this reflects negatively on Python 3.