Review follow-up to #62: docstring indentation and invisible U+202F spaces #63
Reference in New Issue
Block a user
Delete Branch "fix/peer-rate-docstring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Review follow-up to #62, which merged while the review was in flight. No behaviour change — docstring text only, full suite still 1806.
Broken list indentation
Item
2.ofrecompute_category's numbered list sat at column 0 while items1.and3.sit at 4, with its continuation lines at 8 instead of 7.Invisible characters in the formula
Four U+202F NARROW NO-BREAK SPACE characters had been inserted around the operators:
They render identically to a plain space, so they are invisible in review, in a diff, and in the rendered docstring. I found them only by enumerating non-ASCII codepoints in the changed file:
Sigma, the multiplication sign and the dashes stay — those are deliberate and legible. The distinction is the point: a character you can see is a choice; a character you cannot see is a hazard. This repo has just spent a session on that exact failure mode, and
plans/text-integrity-audit.mdconverted its own test fixtures to\uescapes for the same reason.Review notes on #62 itself, for the record
The change it made is correct and I verified it independently rather than taking the report:
outcome_rowsis filtered onoutcome_samples > 0, soΣn ≥ 1.peer_rate = Noneis handled —expected_success_rateguards it (proficiency.py:171,174), and the newelsebranch matches the pre-existing empty case.assert 0.905 == 0.812, so it would catch a regression rather than restating the implementation.Nonescores out of the numerator but divided by the unfilteredlen(outcome_rows), so anyNonedragged the peer rate toward zero.