News for hackers. Stuff that matters.
[dead]
Re:Sunsetting Python 2 by wongarsu on Monday September 09, 2019 @04:54AM (#20916347)
More like

Q) I like Python 2. Can I take over Python 2 maintenence?

A) Sure. Just don't pretend to be us; call your fork something other than Python 2

Re:Sunsetting Python 2 by CJefferson on Monday September 09, 2019 @09:26AM (#20917899)
If I can't make the executable, by default on installing, be 'python2', I'm adding quite a lot of pain to users (in particular, all those users with #!/usr/bin/env python2 in scripts).
Re:Sunsetting Python 2 by partialrecall on Monday September 09, 2019 @12:08PM (#20919430)
Tell your stick-in-the-mud customers to just symlink it. I sincerely doubt you will be sued for telling your customers to symlink `dead-snake` to `python` if they're really stubborn about not changing their code one whit.
Re:Sunsetting Python 2 by mehrdadn on Monday September 09, 2019 @06:16AM (#20916782)
I think "can I take over maintenance" meant "can you give me permission to do this under the existing name".
Re:Sunsetting Python 2 by emiliobumachar on Monday September 09, 2019 @06:17AM (#20916788)
ShedSkin
Re:Sunsetting Python 2 by DonHopkins on Monday September 09, 2019 @05:59AM (#20916712)
Pythoff.
Re:Sunsetting Python 2 by rlayton2 on Monday September 09, 2019 @04:32AM (#20916231)
Is that the stance? I haven't heard anything on that front.

I'm sure there is a great market opportunity for some developers to do the migrations, or to alternative do backporting for some large companies not interested in mingrating.

Re:Sunsetting Python 2 by CJefferson on Monday September 09, 2019 @08:17AM (#20917405)
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".

Re:Sunsetting Python 2 by IshKebab on Monday September 09, 2019 @04:39AM (#20916260)
I don't see how they could sure given that Python is open source. Maybe they own the Python trademark and you'd have to call it something else?
Re:Sunsetting Python 2 by qilo on Monday September 09, 2019 @04:50AM (#20916324)
Yes, you are free to do it, no one is stopping you, but don't call it Python.
Re:Sunsetting Python 2 by WilliamEdward on Monday September 09, 2019 @04:39AM (#20916257)
Why would anyone like python2 so much better than python3 that they would want to fork it into its own language? The two languages are already incredibly similar and python3 has a much larger active community.
Re:Sunsetting Python 2 by bandrami on Monday September 09, 2019 @06:44AM (#20916925)
Because I have 20-year-old code in the wild still running. I know python won't change out from under me; I do not have that confidence in python3.
Re:Sunsetting Python 2 by WilliamEdward on Monday September 09, 2019 @10:00AM (#20918212)
This doesn't make sense; if python 2 continues being developed then it will change for you. Besides, no one says you have to upgrade if you've found a version of 3 that you like, so what exactly is changing out from under you? The leap from 2 to 3 was not even that drastic. The entire changelog is incredibly short.
Re:Sunsetting Python 2 by alexmlamb on Monday September 09, 2019 @05:15AM (#20916471)
It's having to write the parenthesis after print. No one wants that and it's been by far the largest complaint the community has about python3.
Re:Sunsetting Python 2 by paulific on Monday September 09, 2019 @06:14AM (#20916776)
Yup. By no means a developer, but I Python was the first programming language I learned and I always felt it was my native language. I was happy to stick around with 2.7 for as long as it was there, but I guess this is the motivation I needed to learn Ruby or Haskell. :-(
Re:Sunsetting Python 2 by lutoma on Monday September 09, 2019 @06:02AM (#20916722)
> No one wants that

Why would you write a statement that is so demonstrably false?

Re:Sunsetting Python 2 by mehrdadn on Monday September 09, 2019 @06:17AM (#20916786)
Probably because it's hyperbole to get a point across.
Re:Sunsetting Python 2 by jiffyjeff on Monday September 09, 2019 @06:25AM (#20916835)
I don't know if the author was intending to be hyperbolic -- I for one prefer Python 2's print. I would've preferred keeping print the way it was and using a new keyword for the new functionality.
Re:Sunsetting Python 2 by aequitas on Monday September 09, 2019 @07:46AM (#20917219)
The change in the print statement was also what put me off from Python 3 for a long while. But back then there where also no big benefits to be had from moving to 3. Nowadays I even prefer the print function as it makes it easer to convert to log functions.
Re:Sunsetting Python 2 by WilliamEdward on Monday September 09, 2019 @10:02AM (#20918224)
I still don't see why the print function justifies trying to keep the language alive. You don't prefer that print act as a function and not a keyword? Maybe you don't, but is the change really not worth giving up 2?