Drop Python 3.6 and 3.7 support in CI#2417
Closed
EwoutH wants to merge 1 commit intovaexio:masterfrom
Closed
Conversation
This commit drops Python 3.6 and 3.7 in the CI configurations. Both versions are end-of-life and aren't supported or updated anymore. This simplifies the CI configuration and will allow for easier CI upgrades in the future.
Contributor
|
Interesting that the tests are failing, one part is the |
Contributor
Author
|
I'm going to close this in favour of ongoing efforts (like #2331). |
This file contains hidden or 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
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.
This commit drops Python 3.6 and 3.7 in the CI configurations. Both versions are end-of-life and aren't supported or updated anymore.
This simplifies the CI configuration and will allow for easier CI upgrades in the future.
This is part of a multi-PR effort that aims to support modern Python versions and platforms.
1. Removing old Python versions (this PR)
2. Updating the code base to modern Python 3 standards.
3. Updating all the environments and tools used (see #2414)
4. Adding new Python versions (3.11 and 3.12)
5. Adding new platforms (arm64)