News for hackers. Stuff that matters.
Re:Pip has dropped support for Python 2 by ktpsns on Sunday January 24, 2021 @06:42AM (#25891263)
I think some modular approach could have solved the incompatiblity issue, such as "from future import ...". Shorthands could have been invented to define everything in a single line.

Perl5 has similar flags ("use strict"), and Racket brings it even further to define the whole fucking language of the rest of the file ("#lang racket/gui"). Having the language being choosable by the user is against the "zen of python", I guess. In other words: Such an attemp does not feel "pythonic".

Re:Pip has dropped support for Python 2 by orf on Sunday January 24, 2021 @07:06AM (#25891379)
For some syntactical sugar, like print-function, sure. But there are more fundamental changes that couldn’t be papered over.
Re:Pip has dropped support for Python 2 by jamiesonbecker on Sunday January 24, 2021 @10:13AM (#25892653)
Fundamental changes shouldn't have been papered over by calling the new language Python, as it was a fundamentally different language at that point.
Re:Pip has dropped support for Python 2 by orf on Sunday January 24, 2021 @10:31AM (#25892807)
No, it’s the same language but with different semantics around a specific type. That’s not a different language and code can co-exist with a bit of thought.
Re:Pip has dropped support for Python 2 by JasonFruit on Sunday January 24, 2021 @10:54AM (#25892998)
Every language goes through this at some point in its development: flaws that limit future development have to be fixed. Should every language rename itself and split its community at that point? That seems like an extreme response to a common problem.
Re:Pip has dropped support for Python 2 by Chris2048 on Sunday January 24, 2021 @11:31AM (#25893275)
> Should every language rename itself and split its community at that point?

yes. If breaking, fundamental changes are common, that's a problem.

Re:Pip has dropped support for Python 2 by JasonFruit on Sunday January 24, 2021 @05:15PM (#25896721)
That people can make an initial plan that is self-consistent, logical, and foresees and provides for all future use-cases is a basic tenet of waterfall-style development. The history of software engineering does not uphold that principle. Why would it be different for language designers?
Re:Pip has dropped support for Python 2 by Chris2048 on Sunday January 24, 2021 @06:00PM (#25897105)
Just because an unforeseen issue arises, doesn't mean you need to introduce a breaking change right away.
Re:Pip has dropped support for Python 2 by djur on Sunday January 24, 2021 @01:33PM (#25894407)
The "new language" is called Python 3.
Re:Pip has dropped support for Python 2 by a1369209993 on Tuesday January 26, 2021 @08:52PM (#25923339)
Yes, yes it is. And, like "Perl 6" and to a lesser extent "C++", that name is misleading (and therefore bad), because there is already a different language called "Python" (respectively "Perl", "C"), with significant superficial similarities that it could be confused with.
Re:Pip has dropped support for Python 2 by lizmat on Monday February 01, 2021 @09:25AM (#25988922)
Please note that the misleading part of Perl 6 has been fixed by renaming it to the Raku Programming Language (https://raku.org using the #rakulang tag on social media).