On 17 December 2016 at 20:39, brett.cannon email@example.com wrote:
https://hg.python.org/cpython/rev/287d4290b1b4 changeset: 105714:287d4290b1b4 branch: 2.7 parent: 105677:eb02db65e148 user: Brett Cannon firstname.lastname@example.org date: Sat Dec 17 12:38:54 2016 -0800 summary: Update the porting HOWTO
diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst --- a/Doc/howto/pyporting.rst +++ b/Doc/howto/pyporting.rst . . . Have good test coverage
@@ -106,10 +107,11 @@ thumb is that if you want to be confident enough in your test suite that any failures that appear after having tools rewrite your code are actual bugs in the tools and not in your code. If you want a number to aim for, try to get over 80% -coverage (and don't feel bad if you can't easily get past 90%). If you +coverage (and don't feel bad if you can't easily get passed 90%). If you don't already have a tool to measure test coverage then coverage.py_ is recommended.
Hi Brett, why did you make the above change (get past → get passed)? To me, “get past 90%” means achieving over 90%, but “you can’t get passed 90%” would mean that 90% cannot be given (passed) to you. The original made more sense. Another option would be “get over 90%”, consistent with the previous sentence.