Merged
Conversation
0abbafc to
de126cf
Compare
Python 3.8 reached EOL in October 2024, and 3.9 will reach EOL in October 2025. More importantly, redis-py 7.1.0+ requires Python 3.10+, so our Python version support is tied to upstream requirements. Changes: - Update pyproject.toml to require Python >=3.10 - Update redis-py constraint to >=4.2.0,<8.0.0 - Remove 3.8/3.9 from PyPI classifiers - Remove 3.9 and pypy-3.9 from CI test matrix - Update docs to reflect new requirements Closes #706, #730
de126cf to
668ddc8
Compare
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.
Our Python version support is tied to upstream requirements in redis-py. As of redis-py 7.1.0, Python 3.10+ is required.
Additionally:
While we don't jump all the way to redis-py 7.1.0 in this PR, with Python 3.9 EOL and redis-py dropping support, we might as well drop it.
We do raise the minimum redis-py version to 4.2.0 in this PR, which technically is a breaking change. However, 3.5.3 is five years old! It also doesn't support some of the features this library uses, which means we don't actually support 3.5.3 anyway.
Changes
Closes #706, #730