pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.23.8`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.8): pytest-asyncio 0.23.8
[Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.7...v0.23.8)
### 0.23.8 (2024-07-17)
- Fixes a bug that caused duplicate markers in async tests [#813](https://togithub.com/pytest-dev/pytest-asyncio/issues/813)
#### 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](https://togithub.com/pytest-dev/pytest-asyncio/issues/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 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 contains the following updates:
0.23.7->0.23.8Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.23.8`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.8): pytest-asyncio 0.23.8 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.7...v0.23.8) ### 0.23.8 (2024-07-17) - Fixes a bug that caused duplicate markers in async tests [#813](https://togithub.com/pytest-dev/pytest-asyncio/issues/813) #### 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](https://togithub.com/pytest-dev/pytest-asyncio/issues/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 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.