4 ms·
You say that, but the web platform rarely if ever removes features in this way. My web code from 15 years ago works the same as it always did.
by nicoburns 4y ago
You say that, but the web platform rarely if ever removes features in this way. My web code from 15 years ago works the same as it always did.
- rightbyte 4y agoObviously you chose the wrong framework or even worse - none at all. Ye I am whining but only half joking. Breaking backwards compatibility ruins my mood. And Python are getting way to much slack for what they have been doing to the users. People wanting to stick to 2.7 are ridiculed and soon the software security police will start arresting offenders.
- samus 4y agoIf people that want to stick to 2.7 can find a vendor that supplies them security patches, then there is no problem.
- senko 4y agoI recently upgraded a Python 2 + Django 1.x project with no tests to Python 3 and latest Django. Using 2to3, the most trouble I had were db migrations, which I just squashed. The rest were ferreting out str() problems that 2to3 didn't find (eg. redis package happily taking strings but returning bytes by default), Django regexp url changes, and trivial stuff like that. It took a couple of days work. I also wanted to upgrade the frontend part (webpack build of Vue). I stopped after a few hours od going nowhere and am still apprehensive of approaching that particular thing.