Issue 23947: Add mechanism to import stdlib package bypassing user packages (original) (raw)

Issue23947

Created on 2015-04-14 14:45 by steve.dower, last changed 2022-04-11 14:58 by admin.

Messages (2)
msg240896 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-04-14 14:45
There are some situations where the stdlib imports modules that could be absent, notably "import readline" in site.py. This import is expected to fail in some situations, but because sys.path is fully configured it can be importing arbitrary code. To limit these imports to only installed packages, we could add a fake _stdlib module with __path__ set to a restricted set (approximately/exactly(?) what -I uses) and an importlib helper to import it and alias it in sys.modules. Open question about what to do when a user has already imported their own module and it isn't the stdlib one. We discussed displaying a warning in this case. If the import helper is private we should be able to backport to 2.7/3.4 easily enough.
msg240899 - (view)	Author: Brett Cannon (brett.cannon) *	Date: 2015-04-14 15:01
Just so I don't forget, we also discussed introducing something like importlib.import_stdlib_module() which does what Steve mentions. That would handle aliasing in sys.modules cleanly. In the situation where the module is already in sys.modules and not the same module, a warning can be raised.