Antoine Pitrou <pit...@free.fr> added the comment: > So why the mutation? Are you that worried someone is going to import > importlib._bootstrap directly?
Well, importing importlib *does* import importlib._bootstrap, and creates another copy of the module. importlib.__import__ is then wired to _bootstrap.__import__, which is different from the built-in __import__ (potentially using different globals, for example). > This also costs in development complexity because not only do you have > to run 'make' to get changes to be testable, but it also leads to > difficult debugging situations where if you are not totally sure you > got something working you won't find out until you see e.g. that the > standard I/O streams were not initialized. I'm worried that two different copies of importlib will lead to its own difficult debugging situations. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14657> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
