3 ms·
But this is exactly why people keep piling on about python 3, as an "upgrade" it was worse than what tried to replace for 8 years.
by afiori 7y ago
But this is exactly why people keep piling on about python 3, as an "upgrade" it was worse than what tried to replace for 8 years.
- BiteCode_dev 7y agoSure. And now it has been better for the last 5 years, and does solve the problems it intended to solve.
- afiori 7y agoNo one disputes that today's Python 3 is better that today's Python 2, especially for new projects. (A point can be made that Python 2 now is perfectly frozen in time and so 100% stable, but most people do not care that much) The only thing this means is that the botched upgrade did not end up killing Python; it says nothing about whether it was done badly or not. (I have nothing against python, I just believe it is important to understand why and how what happened happened to avoid similar errors in the future)