Florian Bruhin

@nicoddemus Is this something you're going to look into? If not, I think this needs some more context about what should be done.

Please show the full output, and ideally provide an example (e.g. your project as a .zip or repository) which demonstrates the problem. Not much wen can do with so little...

I know nothing about JUnit XML to be honest, but this is already approved and seems reasonable, so I'm merging and backporting it.

@kloczek I've corrected you on this before, but I'll happily do it again: nose is old, but it runs on Python 3 just fine. It's even mentioned [right on their...

It breaks on Python 3.10 due to the `collections.abc` move (how that is a "few modules" and "which are not in-so-good-condition" is beyond me). It works just fine on three...

@DenisKuplyakov I'm not aware of anyone working on this. If there were any news, they would likely be in this issue.

@vyahello see the comment right above yours. I'm not sure what you're trying to achieve by asking the same thing again a month later...

Looks like the doc build failed, thus preventing the auto-merge: ``` /home/runner/work/pytest/pytest/doc/en/explanation/goodpractices.rst:263: WARNING: unknown document: tox:index /home/runner/work/pytest/pytest/doc/en/explanation/goodpractices.rst:263: WARNING: unknown document: tox:example/pytest ``` not quite sure why?

I'm really not a fan of the proposed `expect_failure` API (nor any of the other `expect_*` spellings). Confusion between `pytest.xfail` and `pytest.mark.xfail` is already something I see a lot in...

I'd honestly rather not ressurrect a 2 year old PR (hopefully) so close to the release - seems like a lot of potential to delay things further.