Repository navigation
Pin pytest-asyncio to <=0.21 - #2563
Merged
Merged
Conversation
Contributor
|
I think it is not pytest-asyncio (those are the changes for latest release: https://github.com/pytest-dev/pytest-asyncio/pull/704/files) but some sub-dependency |
Collaborator
Author
It still could be, I think we were going from 0.21.1 to 0.23.* and there was a lot happening between 0.21 and 0.23: pytest-dev/pytest-asyncio@v0.21.1...v0.23.0 |
Collaborator
Author
|
Looks like adding an upper bound to |
antonpirker
approved these changes
Dec 4, 2023
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.
Seems like the recent release of pytest-asyncio 0.23 might have broken some of our tests -- validating that assumption.