[Python-checkins] peps: Mention that tests that cover C-specific issues are a good thing.

brett.cannon python-checkins at python.org
Wed Apr 13 00:04:01 CEST 2011


http://hg.python.org/peps/rev/cb4815d2aba0
changeset:   3866:cb4815d2aba0
user:        Brett Cannon <brett at python.org>
date:        Tue Apr 12 15:03:54 2011 -0700
summary:
  Mention that tests that cover C-specific issues are a good thing.

files:
  pep-0399.txt |  6 +++++-
  1 files changed, 5 insertions(+), 1 deletions(-)


diff --git a/pep-0399.txt b/pep-0399.txt
--- a/pep-0399.txt
+++ b/pep-0399.txt
@@ -148,7 +148,11 @@
 must have 100% branch coverage for the Python code being replaced by
 C code. This will make sure that the new acceleration code will
 operate as much like a drop-in replacement for the Python code is as
-possible.
+possible. Testing should still be done for issues that come up when
+working with C code even if it is not explicitly required to meet the
+coverage requirement, e.g., Tests should be aware that C code typically
+has special paths for things such as built-in types, subclasses of
+built-in types, etc.
 
 Acting as a drop-in replacement also dictates that no public API be
 provided in accelerated code that does not exist in the pure Python

-- 
Repository URL: http://hg.python.org/peps


More information about the Python-checkins mailing list