Require python 3.10+, up from 3.9+ - #841
Merged
Merged
Conversation
consideRatio
force-pushed
the
pr/req-py310
branch
from
January 20, 2025 12:25
6665f0c to
9ec4493
Compare
Collaborator
Author
|
@jacobtomlinson With us both being very low on time, I'll go for a judgment call and self-merge this without further review to use the limited time available to allocate as best as possible. |
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
1 participant
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.
I see dask/distributed requires 3.10+, so I figure we should reduce the complexity of dask-gateway maintenance by requiring that as well.
I'm doing this now since I'm trying to debug issues in test failures (#814), removing py39 which needs to use an older distributed version could reduce some complexity.