forked from pool/python-pytest-asyncio
- update to 0.23.3:
* 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 * Fixes a bug that caused an internal pytest error when collecting .txt files * Fixes a bug that caused an internal pytest error when using module-level skips #701 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 * Introduces pytest_asyncio.is_async_test which returns whether a test item is managed by pytest-asyncio * Removes and pytest trio, mypy, and flaky from the test dependencies * 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 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python:pytest/python-pytest-asyncio?expand=0&rev=36
This commit is contained in:
@@ -1,3 +1,40 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Jan 2 12:01:57 UTC 2024 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
- update to 0.23.3:
|
||||
* 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
|
||||
* Fixes a bug that caused an internal pytest error when
|
||||
collecting .txt files
|
||||
* Fixes a bug that caused an internal pytest error when using
|
||||
module-level skips #701
|
||||
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
|
||||
* Introduces pytest_asyncio.is_async_test which returns whether
|
||||
a test item is managed by pytest-asyncio
|
||||
* Removes and pytest trio, mypy, and flaky from the test
|
||||
dependencies
|
||||
* 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
|
||||
- drop hypothesis-health-check.patch (upstream)
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Nov 7 19:34:40 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
|
Reference in New Issue
Block a user