aiohttp-aiofiles-tutorial
aiohttp-aiofiles-tutorial copied to clipboard
Update dependency pytest-asyncio to v0.23.6
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
pytest-asyncio (changelog) | ==0.20.3 -> ==0.23.6 |
Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.23.6
v0.23.5.post1
: pytest-asyncio 0.23.5.post1
0.23.5 (2024-02-09)
- Declare compatibility with pytest 8 #737
- Fix typing errors with recent versions of mypy #769
- Prevent DeprecationWarning about internal use of
asyncio.get_event_loop()
from affecting test cases #757
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
: pytest-asyncio 0.23.5
0.23.5 (2024-02-09)
- Declare compatibility with pytest 8 #737
- Fix typing errors with recent versions of mypy #769
- Prevent DeprecationWarning about internal use of
asyncio.get_event_loop()
from affecting test cases #757
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.4
: pytest-asyncio 0.23.4
0.23.4 (2024-01-28)
- pytest-asyncio no longer imports additional, unrelated packages during test collection #729
- Addresses further issues that caused an internal pytest error during test collection
- Declares incompatibility with pytest 8 #737
v0.23.3
: pytest-asyncio 0.23.3
0.23.3 (2024-01-01)
- Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #706
- Fixes various bugs that caused an internal pytest error during test collection #711 #713 #719
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.2
0.23.2 (2023-12-04)
- Fixes a bug that caused an internal pytest error when collecting .txt files #703
v0.23.1
: pytest-asyncio 0.23.1
0.23.1 (2023-12-03)
- Fixes a bug that caused an internal pytest error when using module-level skips #701
v0.23.0
: pytest-asyncio 0.23.0
This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22.
- BREAKING: The asyncio_event_loop mark has been removed. Event loops with class, module, package, and session scopes can be requested via the scope keyword argument to the asyncio mark.
- Introduces the event_loop_policy fixture which allows testing with non-default or multiple event loops #662
- Introduces
pytest_asyncio.is_async_test
which returns whether a test item is managed by pytest-asyncio #376 - Removes and pytest-trio, mypy, and flaky from the test dependencies #620, #674, #678
v0.22.0
: pytest-asyncio 0.22.0 (yanked)
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)
- Class-scoped and module-scoped event loops can be requested via the asyncio_event_loop mark. #620
- Deprecate redefinition of the event_loop fixture. #587 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.
- Test items based on asynchronous generators always exit with xfail status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. #642
- Remove support for Python 3.7
- Declare support for Python 3.12
v0.21.1
: pytest-asyncio 0.21.1
0.21.1 (2023-07-12)
- Output a proper error message when an invalid
asyncio_mode
is selected. - Extend warning message about unclosed event loops with additional possible cause. #531
- Previously, some tests reported "skipped" or "xfailed" as a result. Now all tests report a "success" result.
v0.21.0
: pytest-asyncio 0.21.0
0.21.0 (23-03-19)
- Drop compatibility with pytest 6.1. Pytest-asyncio now depends on pytest 7.0 or newer.
- pytest-asyncio cleans up any stale event loops when setting up and tearing down the 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.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.