It's not hard to understand why these things were done that way: idealism and lack of practical experience. I don't know if you ever looked at Python 3.0 but it was a ridiculously broken language and it took three more releases to get it to annacceptable level.
Python 3 is better now than it was before but i would still not trust it to run my stuff as well as 2.x did. Especially because pypy compatibility is more important for me than the nonlocal keyword.
I'm not saying killing 3.x is the only solution but i hope you agree that the roof is on fire. We're all spending lots of time and effort to keep our libraries compatible with python 3 but there are barely any users. What's worse is that Python 3 has lots of new Python users whereas lots of experienced are in the 2.x campt which causes friction.
What do you want me to do? Close my eyes and lie to myself that everything is going to be okay? Lots of people did that and that did not help.
1
u/mitsuhiko Flask Creator May 26 '14
It's not hard to understand why these things were done that way: idealism and lack of practical experience. I don't know if you ever looked at Python 3.0 but it was a ridiculously broken language and it took three more releases to get it to annacceptable level.
Python 3 is better now than it was before but i would still not trust it to run my stuff as well as 2.x did. Especially because pypy compatibility is more important for me than the nonlocal keyword.
I'm not saying killing 3.x is the only solution but i hope you agree that the roof is on fire. We're all spending lots of time and effort to keep our libraries compatible with python 3 but there are barely any users. What's worse is that Python 3 has lots of new Python users whereas lots of experienced are in the 2.x campt which causes friction.
What do you want me to do? Close my eyes and lie to myself that everything is going to be okay? Lots of people did that and that did not help.