[issue16748] Ensure test discovery doesn't break for modules testing C and Python implementations
R. David Murray
report at bugs.python.org
Fri Dec 28 22:12:49 CET 2012
R. David Murray added the comment:
That sounds right to me.
Note that PEP 399 is following older conventions that were laid down in a time when unittest did not *have* test discovery, so this is a new paradigm we'd like to move to (for the reasons Brett mentioned), and it may take a while to get there. It applies to more than just the python/C accelerator distinction; it applies any time a base class plus specialized classes are used to construct test cases. (I do this a bunch in the email tests, for example, and that has no accelerator.)
----------
nosy: +r.david.murray
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16748>
_______________________________________
More information about the Python-bugs-list
mailing list