Re:Where are we in the Python 3 transition?
by lyschoening on Friday January 01, 2016 @04:00PM
(#10823409)
Maybe Python 2 to Python 3.0 didn't introduce many "awesome" features, but 3.4 and 3.5 have been great.
Re:Where are we in the Python 3 transition?
by AnkhMorporkian on Friday January 01, 2016 @04:17PM
(#10823509)
asyncio and pathlib are absolutely killer features for me. I never much cared about Python 3 until asyncio came on the field. As soon as I saw some example code Guido had written, I started using tulip, and have been a willing participant on the wild ride it has taken.
Re:Where are we in the Python 3 transition?
by rspeer on Friday January 01, 2016 @04:44PM
(#10823611)
Pathlib lets me down a bit -- I find myself having to str() the Path objects and lose their benefits, because the rest of the standard library doesn't use pathlib.
But asyncio is great. It shows how much better asynchronous programming can be when you have support from the language itself. I can't imagine going back to a byzantine system like Twisted even if they did manage to finish their Python 3 port.
One thing I think the ruby core team has done a great job of in my opinion is always having some awesome new features in the next major release that make you say "hey thats awesome" and make you want to upgrade despite any headache it might cause and the headaches are generally minimal.
Its been interesting to see python so publicly and painfully fail at that.
A whole new language version release that as far as I can tell only changed internal plumbing and went so far as to make you have rewrite print statements?
I just don't understand how they could think people would want to move to that.