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.
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.
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