#18034: update FAQ to suggest importlib.import_module instead of __import__. Patch...

diff --git a/Doc/faq/programming.rst b/Doc/faq/programming.rst
index e3833938542a9706abd865dfccd8c31204df5d3c..13464b9c465584d400ed1b9efbe7b6a65d7bdd05 100644 (file)
--- a/Doc/faq/programming.rst
+++ b/Doc/faq/programming.rst
@@ -1925,19 +1925,10 @@ These solutions are not mutually exclusive.
 __import__('x.y.z') returns <module 'x'>; how do I get z?
 ---------------------------------------------------------
 
-Try::
-
-   __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`.
+Consider using the convenience function :func:`~importlib.import_module` from
+:mod:`importlib` instead::
 
+   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?

diff --git a/Misc/ACKS b/Misc/ACKS
index 3751fd7a197d105e3897a12a550cd1e6f667c0d3..a5e9b4e757d2d203a2d53000397501a8457ebc75 100644 (file)
--- a/Misc/ACKS
+++ b/Misc/ACKS
@@ -545,6 +545,7 @@ Bernhard Herzog
 Magnus L. Hetland
 Raymond Hettinger
 Kevan Heydon
+Wouter van Heyst
 Kelsey Hightower
 Jason Hildebrand
 Richie Hindle