iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention that tests that cover C-specific issues are a good thing.

This commit is contained in:
Brett Cannon 2011-04-12 15:03:54 -07:00
parent 3acdd3085c
commit 5efdbbb390
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0399.txt
View File

@ -148,7 +148,11 @@ suite is thorough enough to cover all relevant semantics, the tests
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