Michael Seifert
Michael Seifert
@MeggyCal Can you provide a small code example that reproduces the issue? Ideally, this should go into a separate issue.
@MeggyCal A quick look at the logs suggest that the tests due to the following warning: > pytest.PytestWarning: The test […] is marked with '@pytest.mark.asyncio' but it is not an...
Thanks for the investigation, @MeggyCal ! I hope that we can get rid of the blockers soon, which prevent users from upgrading from v0.21…
I'm not ware that anyone is currently working on this. If you can contribute a PR, that's great! Your idea sounds good. You somehow need to access _Config_, in order...
It's not unlikely that pytest-asyncio is at fault here. The plugin has some pretty ugly code that runs during test collection: https://github.com/pytest-dev/pytest-asyncio/blob/v0.23.7/pytest_asyncio/plugin.py#L575-L653 Essentially, it can only deal with standard pytest...
Thanks for the update @bsipocz !
@jamesbraza Thanks for pointing to the pytest issue! I wasn't aware of that. @nierob The _asyncio_default_fixture_loop_scope_ setting only affects async fixtures, not async tests. A similar configuration option for async...
@MarkusBiggus Good catch! I'd absolutely support a PR addressing the wrong param name in the log alongside a small remark in the changelog.
@rysev-a My understanding is that you're proposing that pytest-asyncio removes extraneous quotes from the config param _asyncio_default_fixture_loop_scope_. To be honest, I don't really support this idea, because all the config...