Conversation
bluetech
force-pushed
the
rm-rm-in-9
branch
2 times, most recently
from
78db2a6 to
d53a8e2
Compare
|
The doc build fails. I tried to update sphinx but still fails. Can't reproduce locally. Not sure if it's due to this PR. I'll submit the sphinx upgrade separately to see. |
Per our deprecation policy. Fix pytest-dev#13893.
|
OK, so it's really something in this PR that's causing this sphinx error, but the only change is "9" -> "10", pretty strange. I'll look into it. Maybe switching the |
themavik
left a comment
themavik
left a comment
There was a problem hiding this comment.
Removes PytestRemovedIn9Warning and bumps the deprecation cycle to RemovedIn10. Clean removal with doc and test updates.
Done well: Consistent updates across warning_types, init, warnings.py, and tests. The commented-out filterwarnings("error", ...) in warnings.py with the "To be enabled in pytest 10.0.0" note is clear.
Suggestion: In warnings.py, the PytestRemovedIn10Warning filter is now commented out. Consider adding a brief comment explaining why it stays commented until 10.0 (e.g. "RemovedIn9 items were removed; RemovedIn10 enforcement starts in 10.0") so future maintainers don't wonder.
3 participants
Per our deprecation policy.
Fix #13893.