#18034: update FAQ to suggest importlib.import_module instead of __import__. Patch by Wouter van Heyst.

This commit is contained in:
Ezio Melotti 2014-08-04 19:34:29 +03:00
parent 69fb6a41c5
commit e4aad5ab32
2 changed files with 4 additions and 12 deletions

View file

@ -1786,19 +1786,10 @@ These solutions are not mutually exclusive.
__import__('x.y.z') returns <module 'x'>; how do I get z? __import__('x.y.z') returns <module 'x'>; how do I get z?
--------------------------------------------------------- ---------------------------------------------------------
Try:: Consider using the convenience function :func:`~importlib.import_module` from
:mod:`importlib` instead::
__import__('x.y.z').y.z
For more realistic situations, you may have to do something like ::
m = __import__(s)
for i in s.split(".")[1:]:
m = getattr(m, i)
See :mod:`importlib` for a convenience function called
:func:`~importlib.import_module`.
z = importlib.import_module('x.y.z')
When I edit an imported module and reimport it, the changes don't show up. Why does this happen? When I edit an imported module and reimport it, the changes don't show up. Why does this happen?

View file

@ -549,6 +549,7 @@ Bernhard Herzog
Magnus L. Hetland Magnus L. Hetland
Raymond Hettinger Raymond Hettinger
Kevan Heydon Kevan Heydon
Wouter van Heyst
Kelsey Hightower Kelsey Hightower
Jason Hildebrand Jason Hildebrand
Richie Hindle Richie Hindle