-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency pytest-asyncio to v0.24.0 #53
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/pytest-asyncio-0.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.21.1
Update dependency pytest-asyncio to v0.23.0
Dec 3, 2023
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
December 3, 2023 11:38
01d7c63
to
96fd1d4
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.0
Update dependency pytest-asyncio to v0.23.1
Dec 3, 2023
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
December 3, 2023 23:23
96fd1d4
to
48bc855
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.1
Update dependency pytest-asyncio to v0.23.2
Dec 4, 2023
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
December 4, 2023 09:27
48bc855
to
cecbb63
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.2
Update dependency pytest-asyncio to v0.23.3
Jan 1, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
January 1, 2024 16:14
cecbb63
to
1fa417f
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.3
Update dependency pytest-asyncio to v0.23.4
Jan 28, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
January 28, 2024 20:07
1fa417f
to
8f00003
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.4
Update dependency pytest-asyncio to v0.23.5
Feb 9, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
February 9, 2024 19:33
8f00003
to
d8ec137
Compare
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
March 8, 2024 16:39
d8ec137
to
93c6c0f
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.5
Update dependency pytest-asyncio to v0.23.5.post1
Mar 8, 2024
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.5.post1
Update dependency pytest-asyncio to v0.23.6
Mar 19, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
March 19, 2024 10:20
93c6c0f
to
d92e9b1
Compare
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
May 19, 2024 15:12
d92e9b1
to
42f2728
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.6
Update dependency pytest-asyncio to v0.23.7
May 19, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
July 17, 2024 18:03
42f2728
to
5f64a56
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.7
Update dependency pytest-asyncio to v0.23.8
Jul 17, 2024
renovate
bot
force-pushed
the
renovate/pytest-asyncio-0.x
branch
from
August 22, 2024 10:01
5f64a56
to
79ae546
Compare
renovate
bot
changed the title
Update dependency pytest-asyncio to v0.23.8
Update dependency pytest-asyncio to v0.24.0
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.20.3
->==0.24.0
Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.24.0
: pytest-asyncio 0.24.0Compare Source
0.24.0 (2024-08-22)
pytest_asyncio.fixture
. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.@pytest.mark.asyncio
. #812v0.23.8
: pytest-asyncio 0.23.8Compare Source
0.23.8 (2024-07-17)
Known 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.
v0.23.7
: pytest-asyncio 0.23.7Compare Source
0.23.7 (2024-05-19)
Known 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.
v0.23.6
: pytest-asyncio 0.23.6Compare Source
0.23.6 (2024-03-19)
Known 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.
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.
v0.23.5
: pytest-asyncio 0.23.5Compare 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.
v0.23.4
: pytest-asyncio 0.23.4Compare Source
0.23.4 (2024-01-28)
v0.23.3
: pytest-asyncio 0.23.3Compare Source
0.23.3 (2024-01-01)
Known 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.
v0.23.2
: pytest-asyncio 0.23.2Compare Source
0.23.2 (2023-12-04)
v0.23.1
: pytest-asyncio 0.23.1Compare Source
0.23.1 (2023-12-03)
v0.23.0
: pytest-asyncio 0.23.0Compare Source
This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.
loops with class, module, package, and session scopes can be
requested via the scope keyword argument to the asyncio
mark.
non-default or multiple event loops #662
pytest_asyncio.is_async_test
which returns whether atest item is managed by pytest-asyncio #376
dependencies #620, #674, #678
v0.22.0
: pytest-asyncio 0.22.0 (yanked)Compare Source
This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.
0.22.0 (2023-10-31)
via the asyncio_event_loop mark. #620
Users requiring a class-scoped or module-scoped asyncio event loop for their tests
should mark the corresponding class or module with asyncio_event_loop.
v0.21.2
: pytest-asyncio 0.21.2Compare Source
0.21.2 (2024-04-29)
v0.21.1
: pytest-asyncio 0.21.1Compare Source
0.21.1 (2023-07-12)
asyncio_mode
is selected.#531
v0.21.0
: pytest-asyncio 0.21.0Compare Source
0.21.0 (23-03-19)
event_loop fixture. This behavior has been deprecated and pytest-asyncio emits a
DeprecationWarning when tearing down the event_loop fixture and current event loop
has not been closed.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.