baserev update by copy to link target

• Files Changed
• Browse Source

- update to 0.23.6:
  * compatibiltiy with pytest 8.2

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- remove unnecessary dependency on async_generator
  * Prevent DeprecationWarning to bubble up on CPython 3.10.9 and 3.11.1. #460
- Inject multibuild to defeat a build loop
- Initial release of python-pytest-asyncio 0.8.0

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Add hypothesis-health-check.patch to fix tests

for Staging:F

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 0.21.1:
  * 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.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 0.21.0:
  * 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.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

SR for python stack proposal

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to 0.20.3:
  * Prevent DeprecationWarning to bubble up on CPython 3.10.9 and 3.11.1. #460

• Files Changed
• Browse Source