3 ms·
I didn't say it's a bad change! But since you raise the issue, there are downsides: Many programs developed on 3.7 will inadvertently break on pre-3.7 Python v
by fulafel 9y ago
I didn't say it's a bad change!
But since you raise the issue, there are downsides: Many programs developed on 3.7 will inadvertently break on pre-3.7 Python versions. As we know, this is a big thing on parts of the Python ecosystem because users frequently rely on the Python version that come with their OS or framework (eg AWS Lambda), and many developers want to stay compatible with the most common platform-shipped Python versions.
- ericfrederich 9y agoIt's a good assumption for 3.7. In isolation this is a pragmatic decision and makes sense. You are correct though. A .py file which uses non-ascii and doesn't declare the encoding should be considered an error though. Hopefully everybody's dev tools will pick this up (even on 3.7 where they wouldn't need to)