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 brett.cannon, ezio.melotti, r.david.murray, serhiy.storchaka, zach.ware
Date 2013-07-17.17:18:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
R. David Murray wrote:
> So, the fact that the tests don't run if discovery is used is still a
> bug.  I'm not sure how we fix it, given the nature of the resource.

My preferred solution short of adding resource management to unittest is to add a "regrtest_run" flag to test.support, defaulting to False and set to True by regrtest (like verbose, use_resources, etc.).  Then we can replace the sys._getframe hack in support.requires with a simple check of support.regrtest_run.  If it's False, return.  This way, running the test module directly or via discovery will work the same way: all resources enabled.
History
Date User Action Args
2013-07-17 17:18:54zach.waresetrecipients: + zach.ware, brett.cannon, ezio.melotti, r.david.murray, serhiy.storchaka
2013-07-17 17:18:54zach.waresetmessageid: <[email protected]>
2013-07-17 17:18:54zach.warelinkissue18258 messages
2013-07-17 17:18:54zach.warecreate