Bruno Oliveira

> instead of using pytest.xfail() it would use raise pytest.xfail.Exception which works even with --runxfail I'm probably misunderstanding, but `pytest.xfail` just raises `XFailed`: ```python @_with_exception(XFailed) def xfail(reason: str = "")...

Ahh thanks @bluetech that explains it!

Hi folks, anything else needed here (other than fixing the conflicts)?

@symonk gentle ping 😁

Hi @Dreamsorcerer, > the code within the body will always generate a mypy error which must be ignored Not in general (in fact in almost all cases in my experience),...

Fair enough, that is indeed interesting for testing APIs. I've changed the title to better reflect the request, thanks for writing!

The simple fix would be to add a default to the `getoption` call, so the error will not happen anymore in case the option is not defined, for example `config.getoption("verbose")`...

Hi @ka28kumar, that's great to hear. No need for permission to get started, feel free to fork the project, and submit a PR (even if incomplete).

> I'd prefer if we can add a default value of 0 to the verbose option. What do you mean, add the default to the verbose definition? Note that's already...

> How about an option for the user to suppress pytest's attempts to make a rich diff, and to just to print one, and then print the other, between some...