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 eric.snow
Recipients Arfrever, asvetlov, danielsh, eli.bendersky, eric.snow, r.david.murray
Date 2013-01-26.05:51:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So the current solution is to temporarily put the relevant module in place in sys.modules, right?  That seems to be the solution that Stefan recommended and used in the decimal module.  Sounds good to me.

I'm hitting this while doing the PEP 399 two-step for the collections module.  It seems like this will be a problem for testing any module that has had such attention and has __all__.  I'd be a fan of a class decorator that would take care of this and the rest of the PEP 399 stuff for you.

I've created issue #17037 to cover that (so it doesn't get muddled in with this discussion of test___all__).  There's even a proposed patch.
Date User Action Args
2013-01-26 05:51:01eric.snowsetrecipients: + eric.snow, Arfrever, r.david.murray, eli.bendersky, asvetlov, danielsh
2013-01-26 05:51:00eric.snowsetmessageid: <>
2013-01-26 05:51:00eric.snowlinkissue16817 messages
2013-01-26 05:51:00eric.snowcreate