[Python-Dev] test___all__ polluting sys.modules?
Eli Bendersky
eliben at gmail.com
Mon Dec 31 17:29:51 CET 2012
More information about the Python-Dev mailing list
Mon Dec 31 17:29:51 CET 2012
- Previous message: [Python-Dev] test___all__ polluting sys.modules?
- Next message: [Python-Dev] test___all__ polluting sys.modules?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Dec 31, 2012 at 1:45 AM, Arfrever Frehtes Taifersar Arahesis < arfrever.fta at gmail.com> wrote: > 2012-12-30 15:48:30 R. David Murray napisaĆ(a): > > On Mon, 31 Dec 2012 00:38:47 +1000, Nick Coghlan <ncoghlan at gmail.com> > wrote: > > > However, specifically spinning out the "import the world" tests like > > > test_pydoc and test___all__ to a separate process might be worth the > > > effort. > > > > Adding something to regertest (or unittest?) so that certain nominated > > test modules are run in a subprocess has been discussed previously, but > > so far no one has stepped up to implement it :) > > Actually patches have been implemented about 2 years ago, but nobody > committed them. > http://bugs.python.org/issue1674555 > > > (I think this came up originally for test_site, but I don't remember for > sure.) > > Yes, test_site. > Thank you Arfrever. I'll take a look at those patches. Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20121231/a7eaa679/attachment.html>
- Previous message: [Python-Dev] test___all__ polluting sys.modules?
- Next message: [Python-Dev] test___all__ polluting sys.modules?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list