support py311 locks #348
Merged
support py311 locks #348
Conversation
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
|
The fact that I don't think there is a need to do a post release to include this test coverage, but others may disagree. Anyways, I'm happy to do that if you guys wanted to 👍 |
08bca8f to
03cebd0
Compare
rcomer
approved these changes
Apr 21, 2023
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.
🚀 Pull Request
Description
This PR extends the conda lock file generation to support
py311.After this lands, I'll extend the
toxtesting to coverpy311too, but in a separate PR, as the lock files require to be available before we turn on testing.We can manually run the
ci-locksto auto generated the PR containingpy311dependencies.