Update dependency pytest-asyncio to v0.23.6#540
Merged
Conversation
renovate
Bot
added
dependencies
renovate
Bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
3 times, most recently
from
cd2e90e to
c3793a4
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
c3793a4 to
b0cd195
Compare
renovate
Bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
b0cd195 to
b3ed035
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
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.
This PR contains the following updates:
0.23.5->0.23.6Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.23.6Compare Source
v0.23.5.post1: pytest-asyncio 0.23.5.post1Compare Source
0.23.5 (2024-02-09)
asyncio.get_event_loop()from affecting test cases #757Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
Configuration
📅 Schedule: Branch creation - "before 4am" in timezone America/Chicago, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.