This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients amaury.forgeotdarc, belopolsky, meador.inge, serhiy.storchaka, zach.ware
Date 2014-07-24.20:32:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406233925.87.0.452498118491.issue22060@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a patch that aims to clean up the ctypes tests a bit, namely by removing the custom resource management (which conflicts with regrtest), the custom test discovery (which is better left to unittest), and the custom test running (which is better covered by unittest and regrtest).  The one thing I'm not entirely confident about removing is the custom refleak testing, but it does not seem to work correctly in 3.x anyway (though in 2.7, the custom refleak hunter reports "leaks" that the regrtest refleak hunter does not).

There were only a few uses of the custom resource management, all of which were replaced or removed.  test_SEH in test_win32 used "requires('SEH')", but that test should now be sufficiently guarded with unittest skip decorators (only trying the test on Windows, with Python built in Release configuration by MSVC).  test_PyLong_Long in test_python_api used "requires('refcount')", but that should be covered by the @support.refcount_test decorator (added long after the 'requires' call).  Two instances of "is_resource_enabled('printing')" were replaced by "if test.support.verbose".

The same number of tests run (all successfully) on Windows, I have not yet tested on any other platforms.
History
Date User Action Args
2014-07-24 20:32:06zach.waresetrecipients: + zach.ware, amaury.forgeotdarc, belopolsky, meador.inge, serhiy.storchaka
2014-07-24 20:32:05zach.waresetmessageid: <1406233925.87.0.452498118491.issue22060@psf.upfronthosting.co.za>
2014-07-24 20:32:05zach.warelinkissue22060 messages
2014-07-24 20:32:05zach.warecreate