Commit13e9477

authored and

committed

Link to migration guides from changelog

1 parent4d2cf3c commit13e9477Copy full SHA for 13e9477

File tree

+10

-0

lines changed

+10

-0

lines changed

Lines changed: 2 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+.. _how_to_guides/migrate_from_0_23:`
	`2`	`+`
`1`	`3`	`========================================`
`2`	`4`	`How to migrate from pytest-asyncio v0.23`
`3`	`5`	`========================================`

Lines changed: 8 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -62,6 +62,10 @@ Notes for Downstream Packagers`
`62`	`62`	`1.0.0<https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0>`_ - 2025-05-26
`63`	`63`	`===============================================================================`
`64`	`64`
	`65`	`+..seealso::`
	`66`	`+`
	`67`	+:ref:`How to migrate from pytest-asyncio v0.23<how_to_guides/migrate_from_0_23>`
	`68`	`+`
`65`	`69`	`Removed`
`66`	`70`	`-------`
`67`	`71`
`@@ -211,6 +215,10 @@ As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the t`
`211`	`215`	`This release is backwards-compatible with v0.21.`
`212`	`216`	`Changes are non-breaking, unless you upgrade from v0.22.`
`213`	`217`
	`218`	`+..seealso::`
	`219`	`+`
	`220`	+:ref:`How to migrate from pytest-asyncio v0.21<how_to_guides/migrate_from_0_21>`
	`221`	`+`
`214`	`222`	`- 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.`
`215`	`223`	- Introduces the event_loop_policy fixture which allows testing with non-default or multiple event loops `#662<https://github.com/pytest-dev/pytest-asyncio/pull/662>`_
`216`	`224`	- Introduces ``pytest_asyncio.is_async_test`` which returns whether a test item is managed by pytest-asyncio `#376<https://github.com/pytest-dev/pytest-asyncio/issues/376>`_

Comments

(0)