[issue37636] Deprecate slicing and ordering operations on sys.version

Change by Ruairidh MacLeod : -- nosy: +rkm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37636] Deprecate slicing and ordering operations on sys.version

Anthony Sottile added the comment: I threw together a flake8 plugin which checks for these usage patterns: https://github.com/asottile/flake8-2020 | Code | Description | ||-| | YTT101 |

[issue37636] Deprecate slicing and ordering operations on sys.version

Raymond Hettinger added the comment: > Regarding the "Would releasing 4.0 instead avoid problems?" > Anthony actually did that experiment, too: it broke third > party projects even more impressively than the 3.10 build did. That's good to know. Please thank Anthony for doing his homework.

[issue37636] Deprecate slicing and ordering operations on sys.version

Nick Coghlan added the comment: Regarding the "Would releasing 4.0 instead avoid problems?" Anthony actually did that experiment, too: it broke third party projects even more impressively than the 3.10 build did. I think Serhiy's point is fairly compelling though - check whether or not

[issue37636] Deprecate slicing and ordering operations on sys.version

Change by Philip Dye : -- nosy: +Philip Dye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37636] Deprecate slicing and ordering operations on sys.version

Paul Ganssle added the comment: > So is the proposed change, in a way. At some point, there will be a 4.0 > release, which may or may not break the code in question. I don't think it's a foregone conclusion that there will be a 4.0 release. It could be that we decide that a 4.0 release

[issue37636] Deprecate slicing and ordering operations on sys.version

Serhiy Storchaka added the comment: I think it is better to left this on third-party linters. * It is easy to catch patterns like `sys.version_info[0] == 3` or `sys.version[:3]` in the linter than in the Python compiler or interpreter. Linters are designed for this. * Not always slicing

[issue37636] Deprecate slicing and ordering operations on sys.version

Stefan Behnel added the comment: > Changing the major version number itself is a breaking change So is the proposed change, in a way. At some point, there will be a 4.0 release, which may or may not break the code in question. So, testing for "version_info[0] == 3" is already wrong, because

[issue37636] Deprecate slicing and ordering operations on sys.version

Serhiy Storchaka added the comment: Changing the major version number itself is a breaking change. For example, there is a code that checks sys.version_info[0] == 3 or even sys.version[0] == "3". -- nosy: +serhiy.storchaka ___ Python tracker

[issue37636] Deprecate slicing and ordering operations on sys.version

Raymond Hettinger added the comment: > Rolling to 4.0 implies backward incompatible changes It might or it might not depending on how we communicate it. See Python 2.0 for a precedent. That was not a backward incompatible release. -- ___ Python

[issue37636] Deprecate slicing and ordering operations on sys.version

Josh Rosenberg added the comment: Rolling to 4.0 implies backward incompatible changes; doing just to avoid 3.10 is breaking semantic versioning rules. -- nosy: +josh.r ___ Python tracker

[issue37636] Deprecate slicing and ordering operations on sys.version

Raymond Hettinger added the comment: Have we considered just rolling our next version to 4.0 instead of 3.10? -- nosy: +rhettinger ___ Python tracker ___

[issue37636] Deprecate slicing and ordering operations on sys.version

Change by Anthony Sottile : -- nosy: +Anthony Sottile ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37636] Deprecate slicing and ordering operations on sys.version

New submission from Nick Coghlan : At the core dev sprints in 2017 (IIRC), Ezio and I were talking about some of the potential issues with 3.10, and one of them was folks attempting to manipulate sys.version with string operations rather than using the already decomposed sys.version info.