8.0.1 release planning

[bluetech]

I plan to release pytest 8.0.1 this weekend (Friday or Saturday), we have fixed many regressions.

Current nice-to-haves that are not yet merged:

• pytest.warns multiple argument handling #11917 (waiting on author)
• Allow using warnings.warn() with a Warning #11959 (maybe; might be only relevant for 8.1, need to check)
• recwarn: let base exceptions propagate through pytest.warns again #11920 (waiting on review)
• Fix collection of short paths on Windows #11936 (maybe; might wait for next patch release depending on review time and whether @nicoddemus would want to backport)

[0x78f1935]

Hi @bluetech, this probably doesn't have anything to do with Pytest, but with pytest-coverage. Yet I was wondering if this version might solve my issue

[bluetech]

@0x78f1935 The issue you're describing doesn't sound familiar to me, so probably not. You say in the issue that it happens on py3.12 but not on py3.11 so it sounds like maybe a Python issue? (I know that py3.12 had some coverage changes so maybe try running python manage.py test with coverage and see if it reproduces)

[0x78f1935]

@bluetech Thank you for your response! I don't think the coverage plugin was compatible with the Django management file, but I'll have to check that again to verify this statement. If I have any updates, I'll update the issue!