SLFO-pool/python-pytest-asyncio
SHA256
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync from SUSE:SLFO:Main python-pytest-asyncio revision ec626b9bae06ef1af44f8533d38e800c

Browse Source
This commit is contained in:
Adrian Schröter
2024-12-13 12:08:17 +01:00
parent 9f1d44614e
commit dedd673f30
6 changed files with 199 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

104
python-pytest-asyncio.changes
View File

@@ -1,3 +1,101 @@
-------------------------------------------------------------------
Tue Jul 9 13:43:10 UTC 2024 - Markéta Machová <mmachova@suse.com>
- Add duplicated-markers.patch to fix some testsuites broken by
that issue.
-------------------------------------------------------------------
Thu Jun 6 20:26:26 UTC 2024 - Dirk Müller <dmueller@suse.com>
- update to 0.23.7:
* Silence deprecation warnings about unclosed event loops that
occurred with certain CPython patch releases
-------------------------------------------------------------------
Thu Mar 21 17:04:18 UTC 2024 - Dirk Müller <dmueller@suse.com>
- update to 0.23.6:
* compatibiltiy with pytest 8.2
-------------------------------------------------------------------
Sat Mar 16 09:46:24 UTC 2024 - Dirk Müller <dmueller@suse.com>
- update to 0.23.5.post1:
* Declare compatibility with pytest 8
* Fix typing errors with recent versions of mypy #769
* Prevent DeprecationWarning about internal use of
`asyncio.get_event_loop()` from affecting test cases #757
-------------------------------------------------------------------
Sat Mar 2 11:29:53 UTC 2024 - Ben Greiner <code@bnavigator.de>
- Update to 0.23.5
* 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.
- Release 0.23.4
* 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
-------------------------------------------------------------------
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>
- remove unnecessary dependency on async_generator
-------------------------------------------------------------------
Tue Oct 17 08:19:39 UTC 2023 - Markéta Machová <mmachova@suse.com>
@@ -37,7 +135,7 @@ Thu Apr 13 22:43:58 UTC 2023 - Matej Cepl <mcepl@suse.com>
Fri Dec 9 11:11:04 UTC 2022 - Daniel Garcia <daniel.garcia@suse.com>
- Update to 0.20.3:
* Prevent DeprecationWarning to bubble up on CPython 3.10.9 and 3.11.1. #460
* Prevent DeprecationWarning to bubble up on CPython 3.10.9 and 3.11.1. #460
-------------------------------------------------------------------
Wed Nov 30 07:13:34 UTC 2022 - Daniel Garcia <daniel.garcia@suse.com>
@@ -71,7 +169,7 @@ Fri Aug 5 04:57:24 UTC 2022 - John Vandenberg <jayvdb@gmail.com>
-------------------------------------------------------------------
Wed Jul 6 07:59:54 UTC 2022 - Steve Kowalik <steven.kowalik@suse.com>
- Inject multibuild to defeat a build loop
- Inject multibuild to defeat a build loop
-------------------------------------------------------------------
Tue Jun 28 19:00:14 UTC 2022 - Ben Greiner <code@bnavigator.de>
@@ -193,4 +291,4 @@ Tue Sep 4 13:10:57 UTC 2018 - Ondřej Súkup <mimi.vx@gmail.com>
-------------------------------------------------------------------
Fri Jan 5 09:47:11 UTC 2018 - alarrosa@suse.com
- Initial release of python-pytest-asyncio 0.8.0
- Initial release of python-pytest-asyncio 0.8.0