[New-bugs-announce] [issue12633] sys.modules gets special treatment
report at bugs.python.org
Mon Jul 25 06:49:50 CEST 2011
New submission from Eric Snow <ericsnowcurrently at gmail.com>:
The sys.modules dict is a special object. It is the only variable of the CPython interpreter object that is exposed in the sys module. Everything else in sys lives in the module. However, the modules dict lives in the interpreter object and is bound to the sys module separately. No other variable of the interpreter object gets this treatment.
This situation sets up an unexpected behavior for sys.modules. There are many places, mostly in Python/import.c, where the modules dict gets used and not by pulling from sys.modules. These places use interp->modules directly. So if sys.modules is re-bound, the imp module is using/reporting an out of sync modules dict.
One could argue that re-binding a module global is risky and should be avoided. I agree. Here is the use case that prompted me to march ahead anyway:
cls.sysmodules = sys.modules
sys.modules = sys.modules.copy()
sys.modules = cls.sysmodules
I was writing some import related tests and wanted sys.modules to be returned to its initial state after each test. I realise that Lib/test/support.py provides CleanImport and others address this, but you have to provide the module names to clean up. This is an unfortunate hassle sometimes when several layers of imports happen during the import of the module you care about.
So the result was an exception when I tried importing an extension module, like "_sqlite3". This is because in importdl.h the new module is added to the dict returned by PyImport_GetModuleDict(), not to the one at sys.modules.
For now I am doing the following to get the same effect:
cls.sysmodules = sys.modules.copy()
for name in sys.modules:
for name in cls.sysmodules:
sys.modules[name] = cls.sysmodules[name]
However, this is less efficient, sort of. I expect that the current direct use of interp->modules in the CPython code is [much?] more efficient than PySys_GetObject("modules") calls.
In light of all this I recommend that either use of interp->modules be replaced by PySys_GetObject("modules") calls, or the sys module documentation be updated to make clear that sys.modules should not be re-bound (in a CPython implementation detail note). I'm guessing that the first option is right out. The documentation addition would be just right.
 variables of the interpreter object found by grepping "interp->" in the CPython source:
 see PyImport_GetModuleDict() in Python/import.c
nosy: ericsnow, ncoghlan
title: sys.modules gets special treatment
versions: Python 3.3
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce