__main__.py Multiprocessing on Windows

[pthiem]

BPO	17101
Nosy	@vstinner

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2019-09-24.10:41:04.949>
created_at = <Date 2013-02-01.16:54:16.552>
labels = ['type-bug', 'library', 'OS-windows']
title = '__main__.py Multiprocessing on Windows'
updated_at = <Date 2019-09-24.10:41:04.947>
user = 'https://bugs.python.org/pthiem'

bugs.python.org fields:

activity = <Date 2019-09-24.10:41:04.947>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2019-09-24.10:41:04.949>
closer = 'vstinner'
components = ['Library (Lib)', 'Windows']
creation = <Date 2013-02-01.16:54:16.552>
creator = 'pthiem'
dependencies = []
files = []
hgrepos = []
issue_num = 17101
keywords = []
message_count = 3.0
messages = ['181090', '223247', '353068']
nosy_count = 3.0
nosy_names = ['vstinner', 'sbt', 'pthiem']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17101'
versions = ['Python 2.7']

[pthiem]

http://bugs.python.org/issue10845 also applies to the 2.X series.

this is multiprocessing on windows has issues with __main__.py

[BreamoreBoy]

Is it possible to backport the fix from bpo-10845 to 2.7? Is it actually worth doing?

[vstinner]

Is it possible to backport the fix from bpo-10845 to 2.7? Is it actually worth doing?

I close the issue, it has been done in 2015:

commit 2a6c2c9
Author: Nick Coghlan <ncoghlan@gmail.com>
Date: Thu Nov 19 12:59:39 2015 +1000

Close bpo-10128: don't rerun __main__.py in multiprocessing

- backports issue bpo-10845's mitigation of incompatibilities between
  the multiprocessing module and directory and zipfile execution
- Multiprocessing on Windows will now automatically skip rerunning top
  level __main__.py modules in spawned processes, rather than failing
  with AssertionError