Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120309/014ae4a7/attachment.html below:
<div><br></div><div>While testing Python 2.7 internally (at Google) I noticed that (now that ImportErrors aren't automatically test skips) lots of tests fail if you don't have the _testcapi module. These tests are (as far as I've seen) properly marked as cpython-only, but when some wacko decides the _testcapi module shouldn't, for example, be shipped to a million machines[*] that are never going to use it, it would be nice to still run the tests that can be run without _testcapi. Any objections to fixing the tests to use test.support.import_module() for _testcapi and a 'needs_testcapi' skipping decorator?</div>
<div><br></div><div>To elaborate, we are also not shipping a couple of other modules (like distutils), but it's not unreasonable to expect those to exist (we modify the testsuite for that in our own builds only, instead, as well as making all our code deal with it.) The _testcapi module, however, is internal *and* meant for tests only, and used in quite a few tests (sometimes only in a single testfunction.)Â </div>
<div><br></div><div>[*] 'a million machines' is not the actual number -- I don't know the actual number (but I'm sure it's bigger than that), I'm just tossing out some large number.</div>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br>
<br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!<br>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4