Bruno Oliveira

@avats-dev thanks for the offer! However this is only done near the actual release (and actually this is incorrect, we do this in 7.1, I've updated the milestone), and we're...

Sure, thanks for the ping, I will work on it. The idea is that we configure `PytestDeprecationWarnings` to errors (the core of it is in #7362, in `src/_pytest/warnings.py`).

Hi @fish-face, Thanks for the report. Would you like to contribute a PR with that? I think a single paragraph to the docs of `request.addfinalizer` would do.

Oh I see, sorry didn't realize that. This is easy to verify by yourself, no need to look at the code: ```python import pytest from functools import partial @pytest.fixture def...

Yeah, sounds great, thanks. I think just a paragraph stating that they are executed in first-in-last-out order is enough. 👍

Not yet.

For reference: #1660

@TvoroG, `pytest-fixture-mark` seems very nice! I hope I get the chance to try it soon! 😄 Perhaps discussion specific to it should be moved to https://github.com/TvoroG/pytest-fixture-mark thought? 😉

I like how it played out, but @hackebrot and @hpk42 had something else in mind during the sprint. 😁 Perhaps they can comment on this.

Hi @kloczek, Thanks for the report! I gave this a shot, the problem is some aliases we have. About `TimeoutExpired`, we declare it in `Pytester`: ```python @final class Pytester: ......