[Python-Dev] test___all__ polluting sys.modules? (original) (raw)
Andrew Svetlov andrew.svetlov at gmail.com
Sun Dec 30 01:48:13 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 ]
See (unfinished but trivial enough) http://bugs.python.org/issue14715 for proposed way to modules/importsystem cleanup
On Sun, Dec 30, 2012 at 2:31 AM, Eli Bendersky <eliben at gmail.com> wrote:
Hi,
This came up while investigating some test-order-dependency failures in issue 16076. test_all goes over modules that have
_all_
in them and does 'from_ import *' on them. This leaves a lot of modules in sys.modules, which may interfere with some tests that do fancy things with sys,modules. In particular, the ElementTree tests have trouble with it because they carefully set up the imports to get the C or the Python version of etree (see issues 15083 and 15075). Would it make sense to save the sys.modules state and restore it in test_all so that sys.modules isn't affected by this test?_ Eli
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.com
-- Thanks, Andrew Svetlov
- 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 ]