Python 2.8?
lwn.net
Python 2.8?
1–10 of 74 posts
Re: Python 2.8?
#2[deleted]
Re: Python 2.8?
#3The 2.X => 3.X transition really appears to have been bungled here, which is a shame. I really liked Python before I got deeply into the .Net world, but it has become less than enticing with this fragmentation. Meanwhile other languages seem to have taken up the vanguard position, which leaves Python in kind of an awkward position, between the new hotness and the tried-and-true enterprisey ecosystems
Re: Python 2.8?
#4The amount of trolling in that thread is incredible. I don't understand why an average Joe needs to contradict Guido on trademark matters.
Re: Python 2.8?
#5The 2.X => 3.X transition really appears to have been bungled here, which is a shame. I really liked Python before I got deeply into the .Net world, but it has become less than enticing with this fragmentation. Meanwhile other languages seem to have taken up the vanguard position, which leaves Python in kind of an awkward position, between the new hotness and the tried-and-true enterprisey ecosystems
I don't think it's "appears to have been" at this point. Python 3 was released in 2008. Python 3 is now older than Python 2 was on the day Python 3 was released.
Re: Python 2.8?
#6The fork should be called "Lython" as in Legacy Python.
Re: Python 2.8?
#7I'm glad Guido considers this a toy. Anyone interested in helping out the github repo is here:
Re: Python 2.8?
#8The 2.X => 3.X transition really appears to have been bungled here, which is a shame. I really liked Python before I got deeply into the .Net world, but it has become less than enticing with this fragmentation. Meanwhile other languages seem to have taken up the vanguard position, which leaves Python in kind of an awkward position, between the new hotness and the tried-and-true enterprisey ecosystems
>The 2.X => 3.X transition really appears to have been bungled here, which is a shame.
Obviously, the question is what went wrong.
Personally I think the dev team gave users too much time to switch.
The Python devs should have only given users one or two years to upgrade. Making it clear that all support for Python 2 would end after that period.
Another mistake was that when originally released Python 3 did not offer enough shiny new things to convince people that going through the pain of upgrading was worthwhile.
They made this worse by backporting features from Python 3 to Python 2, something they should have never done. Python 2 should not have gotten any new features after the release of Python 3.
Python 3 advocates like to blame the users for not upgrading, but I think that is / was simply the result of the actions of the dev team which made staying with Python 2 too comfortable and moving to Python 3 not attractive enough.
Re: Python 2.8?
#9The 2.X => 3.X transition really appears to have been bungled here, which is a shame. I really liked Python before I got deeply into the .Net world, but it has become less than enticing with this fragmentation. Meanwhile other languages seem to have taken up the vanguard position, which leaves Python in kind of an awkward position, between the new hotness and the tried-and-true enterprisey ecosystems
>The 2.X => 3.X transition really appears to have been bungled here, which is a shame. Obviously, the question is what went wrong. Personally I think the dev team gave users too much time to switch. The Python devs should have only given users one or two years to upgrade. Making it clear that all support for Python 2 would end after that period. Another mistake was that when originally released Python 3 did not offer…
No, the problem is that Python 3 sucked, and still sucks.
Twisting your user's arms even more painfully won't solve the problem, it will just accelerate users switching away to other languages or forks.
Re: Python 2.8?
#10The amount of trolling in that thread is incredible. I don't understand why an average Joe needs to contradict Guido on trademark matters.
Because some people are hateful by nature and see Guido as Satan incarnate for "hating Python 2".
And no, I'm not exaggerating, you just need to look at the comments:
https://github.com/naftaliharris/placeholder/issues/47#issue...
I read through that thread the other day and it breaks my heart to know that there are people who think like that. Honestly.
On various occasions I've reasoned (and not reasoned) with the most absurd people, there is always some way to understand where the craziest of logic comes from. But here, I'm just sad.
And I'm especially sad because I've seen similar comments on HN (even just the other day). So really, this goes out to anyone who works in tech and feels like this either about Python or about any open source project: Treat your FOSS maintainers with some human decency.
It's not the first time I say it, and every time I say it there's always some people nodding at this; "oh yes, of course, well who acts like that really?", those same people turning around a week later, flaming Lennart Poettering for whatever software du jour the guy wrote.
sighs