Aleksandr Brodin

> this looks good to me, how does this interact with pytest-asyncio? For pytest-asyncio, everything should work without additional improvements

Probably a more correct solution would be to transfer the completion of the fixtures to an independent hook pytest_fixture_teardown.

> I agree that the problem described in the issue is worth solving. > > To me the original idea of passing the exception(s) to `pytest_fixture_post_finalizer` seems better than adding...

> @ShurikMen I wonder, is the example you gave realistic or do you use `indirect` params maybe? I'm mainly curious why you're setting `scope='class'` on your `parametrize`s when the parameters...

@bluetech take a look at #12082

I have updated the pr. Unified indexing of parameters added through a marker and through fixtures. I think it's the right thing to do. Along the way, I corrected the...

@bluetech what about solving the problem on this issue?

> Marking "Request changes" as per my comment on the issue: [#12163 (comment)](https://github.com/pytest-dev/pytest/issues/12163#issuecomment-2096797077) > > @ShurikMen @rplevka please let me know in the issue if you have any specific use...

same problem on archlinux/python3.13/net-snmp5.9.4, ubuntu22.04/python3.12/net-snmp5.8 ``` 17:35 $ uv venv Using CPython 3.13.3 interpreter at: /usr/bin/python Creating virtual environment at: .venv Activate with: source .venv/bin/activate ✔ ~ 17:35 $ uv...

@carlkidcrypto broken ``` 09:15 $ uv run python -V Python 3.13.7 09:20 $ uv pip freeze | grep ezsnmp ezsnmp==2.1.0a1 09:16 $ net-snmp-config --version 5.9.4.pre2 09:15 $ uv run python...