Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin Pytest-asyncio to <=0.16.0 #17

Closed
nocarryr opened this issue Apr 27, 2022 · 0 comments
Closed

Pin Pytest-asyncio to <=0.16.0 #17

nocarryr opened this issue Apr 27, 2022 · 0 comments

Comments

@nocarryr
Copy link
Owner

The warning added in 0.18.3 (pytest-dev/pytest-asyncio#242) is easily removed by adding the asyncio_mode = auto option in pytest's config.

However, if testing in Python<3.7, this creates another warning with pytest not recognizing the option since as of 0.17.a0, Python3.6 support was dropped (pytest-dev/pytest-asyncio#237).

In most cases, this wouldn't be an issue except when your tests include assertions about warnings using pytest.warns() (not an uncommon practice).

Consider either dropping Py3.6 support or pinning pytest-asyncio to 0.16.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant