pytest.
slightly more difficult to test using normal testing tools. pytest-asyncio
2024-03-20 14:41:17 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 0.23.6
0.23.6 (2024-03-19)
===================
- Fix compatibility with pytest 8.2
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. 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.
|
2024-02-10 08:28:10 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 0.23.5
0.23.5 (2024-02-09)
===================
- Declare compatibility with pytest 8
- Fix typing errors with recent versions of mypy
- Prevent DeprecationWarning about internal use of `asyncio.get_event_loop()` \
from affecting test cases
|
2024-01-29 10:35:22 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 0.23.4
0.23.4 (2024-01-28)
===================
- pytest-asyncio no longer imports additional, unrelated packages during test \
collection
- Addresses further issues that caused an internal pytest error during test \
collection
- Declares incompatibility with pytest 8
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. 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.
|
2024-01-01 18:03:13 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 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
Fixes various bugs that caused an internal pytest error during test collection
|
2023-12-05 18:58:43 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 0.23.2
0.23.2 (2023-12-04)
===================
- Fixes a bug that caused an internal pytest error when collecting .txt files
0.23.1 (2023-12-03)
===================
- Fixes a bug that caused an internal pytest error when using module-level skips
0.23.0 (2023-12-03)
===================
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
0.22.0 (2023-10-31)
===================
This release has been yanked from PyPI due to fundamental issues with the \
_asyncio_event_loop_ mark.
- Class-scoped and module-scoped event loops can be requested
via the _asyncio_event_loop_ mark.
- Deprecate redefinition of the `event_loop` fixture.
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.
- Remove support for Python 3.7
- Declare support for Python 3.12
|
2023-10-28 21:57:26 by Thomas Klausner | Files touched by this commit (516) | |
Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation
This follows the recommended bootstrap method (flit_core, build, installer).
However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.
|
2023-07-17 10:59:48 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 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.
- Previously, some tests reported "skipped" or "xfailed" as \
a result. Now all tests report a "success" result.
|
2023-03-20 09:54:19 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-asyncio: updated to 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.
|