ci: Drop support for python versions before v3.8 #371
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jdehaan
force-pushed
the
ci/disable-python2-checks
branch
from
be312e9
to
d5db9da
Compare
jdehaan
commented
Mar 17, 2023
| @@ -1,7 +1,9 @@ | |||
| image: Visual Studio 2022 | |||
There was a problem hiding this comment.
Defaults otherwise to 2015 if not set explicitly, which does not have a python 3.10...
|
I haven't been involved much in Python development for years. Is it time to drop Python 2 support? |
|
Absolutely. Python2 have been EOL since 4 years ago. Most Linux distros don't support python2 packages anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a matter of facts, I could not make the current codebase work at all under python2. IMHO this is also a waste of time and energy.
Current status of the python maintenance for each version.
https://devguide.python.org/versions/
Reasonably, I propose to support from v3.8 upwards, any older v3 might work... I updated the documentation and the CI configurations to have a more modern setup.
NOTE: I did not update the website generation related things. The changeset deals with the lizard tool alone