From: Brett Cannon <brett@python.org>
Date: Sat, 15 Jun 2013 17:23:01 +0000 (-0400)
Subject: Issue #17177: Stop using imp in multiprocessing
X-Git-Tag: v3.4.0a1~492
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4f4088eb6f768b0af66d6cf682651d7c6a8011b1;p=thirdparty%2FPython%2Fcpython.git

Issue #17177: Stop using imp in multiprocessing
---

diff --git a/Lib/multiprocessing/forking.py b/Lib/multiprocessing/forking.py
index 8841e4e9fcaa..d06036d88335 100644
--- a/Lib/multiprocessing/forking.py
+++ b/Lib/multiprocessing/forking.py
@@ -449,8 +449,8 @@ def prepare(data):
         elif main_name != 'ipython':
             # Main modules not actually called __main__.py may
             # contain additional code that should still be executed
-            import imp
             import importlib
+            import types
 
             if main_path is None:
                 dirs = None
@@ -465,7 +465,7 @@ def prepare(data):
             # since that would execute 'if __name__ == "__main__"'
             # clauses, potentially causing a psuedo fork bomb.
             loader = importlib.find_loader(main_name, path=dirs)
-            main_module = imp.new_module(main_name)
+            main_module = types.ModuleType(main_name)
             try:
                 loader.init_module_attrs(main_module)
             except AttributeError:  # init_module_attrs is optional