- update to 0.23.6:
  * compatibiltiy with pytest 8.2

• 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

• 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

• 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

- 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

• Files Changed
• Browse Source

- Update to 0.20.3:
  * Prevent DeprecationWarning to bubble up on CPython 3.10.9 and 3.11.1. #460 
- Update to 0.20.2:
  * Fixes an issue with async fixtures that are defined as methods on a test
    class not being rebound to the actual test instance. #197
  * Replaced usage of deprecated @pytest.mark.tryfirst with
    @pytest.hookimpl(tryfirst=True) #438
- 0.20.1 (22-10-21)
  * Fixes an issue that warned about using an old version of pytest, even
    though the most recent version was installed. #430
- 0.20.0 (22-10-21)
  * BREAKING: Removed legacy mode. If you're upgrading from v0.19 and you
    haven't configured asyncio_mode = legacy, you can upgrade without taking
    any additional action. If you're upgrading from an earlier version or you
    have explicitly enabled legacy mode, you need to switch to auto or strict
    mode before upgrading to this version.
  * Deprecate use of pytest v6.
  * Fixed an issue which prevented fixture setup from being cached. #404

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Inject multibuild to defeat a build loop 

- Update to 0.18.3
  * Adds pytest-trio to the test dependencies
  * Fixes a bug that caused pytest-asyncio to try to set up async
    pytest_trio fixtures in strict mode. #298
- Release 0.18.2
  * Fix asyncio auto mode not marking static methods. #295
  * Fix a compatibility issue with Hypothesis 6.39.0. #302
- Release 0.18.1
  * Fixes a regression that prevented async fixtures from working
    in synchronous tests. #286
- Release 0.18.0
  * Raise a warning if @pytest.mark.asyncio is applied to non-async
    function. #275
  * Support parametrized event_loop fixture. #278

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Update to 0.14.0
  * Fix #162, and event_loop fixture behavior now is coherent on all scopes.

• Files Changed
• Browse Source

- Update to 0.12.0:
  * Run the event loop fixture as soon as possible.

- Update to 0.11.0:
  * Fix with pytest 5.4

• Files Changed
• Browse Source

py38 fix

• Files Changed
• Browse Source

- Update to 0.10.0:
  * support for pytest 4+

• Files Changed
• Browse Source

- update to 0.9.0
- use github tarbal due packaging errrors in upstream
 * Python 3.7 support.
 * Remove event_loop_process_pool fixture
     and pytest.mark.asyncio_process_pool marker (forwarded request 633033 from mimi_vx)

• Files Changed
• Browse Source

New package python-pytest-asyncio, required by python-pyee, which is
required by mycroft-core

• Browse Source