Florian Bruhin

This seems like a duplicate of #9248.

> Given how monkeypatch works, undo undoes all of them, using the context context manager may be the better detail to recommend Why not both? We added `.context()` in #10143.

What's also a consequence of this - and is pretty annoying with long outputs - is that they're printed twice if there's an issue both during call and teardown: ```...

This is the full output: ``` ============================= test session starts ============================== collected 0 items / 1 error ==================================== ERRORS ==================================== _________________________ ERROR collecting test_add.py _________________________ test_add.py::test_add: in "parametrize" the number...

I'd be okay with a simple change to the error message, but anything more complex really doesn't seem to be worth the trouble, IMHO. I really don't think the error...

Does this only affect `@with_setup`, or also undecorated plain `setup` and `teardown` methods on test classes? The latter is technically part of our nose support, but as far as I'm...

FWIW this seems like a good overview of possibilities (some of which @webknjaz has already mentioned): https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs

That seems expected to me.

I think it'd be quite unusual to do additional type checking here ([EAFP](https://docs.python.org/3/glossary.html#term-eafp) applies :wink:). You'll probably get similar error messages if you do `pytest.approx({'a': None})` or whatever.

@Darkdragon84 nothing I'm aware of - if anything is happening, it would likely be noted in this issue.