2 ms·
I tried Python 3 recently. I honestly can't see that much difference. I had to alter print statements to print functions, and change "Exception , e" to "Excepti
by collyw 13y ago
I tried Python 3 recently. I honestly can't see that much difference. I had to alter print statements to print functions, and change "Exception , e" to "Exception as e". To be honest I couldn't see what the fuss was about.
Now, the real problem was libraries. 90% of the libraries I wanted to use had been ported to Python3 , but there were two or three that hadn't. That basically put me back to Python 2.7. (From a comment on here apparently one of the said libraries now has been converted).
So I guess if you wanted to be proactive you could look at some popular libraries that haven't been ported to Python 3 and start writing.
- allendoerfer 13y agoI look at it this way, too. The brutal approach has been chosen, we can argue about it's effectiveness or individual choices, but the only way we could make it worse would be to start all over again, this long in the game. There is nothing special about legacy software not functional under the most recent version. Ask the java folks in big enterprises. I highly prefer this approach with a strong focus on a clean API than the other way around. We should stop arguing about wrong choices and start start losing graciously [0] and fix the missing pieces. [0] http://www.markshuttleworth.com/archives/1316 http://www.markshuttleworth.com/archives/1316
- lifeisstillgood 13y agoAbsolutely this - lose gracefully and start helping fix the remaining problems