Self-caught while verifying my own correction, which is the point at which it should have been
caught the previous three times.
The note added last commit argues that no figure should be given for how many failures name the
second assignment, because such counts are artifacts of pytest display flags. It then offered
"7 under the default display and 31 under `--tb=long -vv`" as evidence. The 7 is reproducible.
The 31 was taken from a review report and never re-measured; counting the same way against
`--tb=long -vv` gives 62, so either 31 is a different counting or it is wrong, and I cannot tell
which. Quoting a number from a report instead of reproducing it is the exact failure the note
was written to prevent, committed inside the note.
Every figure is gone from all three sites. What survives is the MECHANISM of the trap — a
`grep -c` counts lines and `--tb=line` prints each matching failure twice, so it overstates;
raising the traceback detail moves it the other way — plus the qualitative "about half the suite
reddens", which is coarse enough to be robust. Reproducing any exact figure needs per-failure
parsing rather than grepping, and that is now what the note says instead of demonstrating it
with numbers.
Also dropped "36 of 75" from the guard comment. It reproduces today, but a note whose argument
is that counts drift as tests are added should not carry one.
No code changed. Full suite 1278 passed / 2 skipped; catalog in sync; decisions-validate OK.
fixes#845
Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019zUmJZHhVP7kXg5DV237TW
timothyandClaude Opus 5
f7d6c737f1