This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Update multiprocessing.spawn to use runpy.run_path
Type: Stage: test needed
Components: Library (Lib) Versions: Python 3.5
Status: open Resolution:
Dependencies: 19697 19946 19982 Superseder:
Assigned To: Nosy List: brett.cannon, jnoller, nanjekyejoannah, ncoghlan, sbt
Priority: normal Keywords:

Created on 2013-12-13 16:44 by brett.cannon, last changed 2022-04-11 14:57 by admin.

Messages (2)
msg206117 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2013-12-13 16:44
Once the 'target' parameter for runpy.run_path lands then multiprocessing.spawn should be updated to use it.
msg349122 - (view) Author: Joannah Nanjekye (nanjekyejoannah) * (Python committer) Date: 2019-08-06 17:41
Working on issue 19982 is important prior to this.
Date User Action Args
2022-04-11 14:57:55adminsetgithub: 64177
2019-08-06 17:41:06nanjekyejoannahsetmessages: + msg349122
2019-07-02 14:44:52nanjekyejoannahsetnosy: + nanjekyejoannah
2013-12-14 13:22:30ncoghlansetdependencies: + Add a "target" parameter to runpy.run_path and runpy.run_module
2013-12-14 13:18:47ncoghlansetdependencies: + Handle a non-importable __main__ in multiprocessing
2013-12-13 19:53:20brett.cannonsetdependencies: + Document the possible values for __main__.__spec__
2013-12-13 16:44:41brett.cannoncreate