Message 270343 - Python tracker

➜

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.

Author	eryksun
Recipients	eryksun, neologix, pietvo, pitrou, sbt, tim.peters
Date	2016-07-13.20:30:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
In 3.4+ it works correctly with the "spawn" start method. This uses multiprocessing.spawn.spawn_main, which exits the child via sys.exit(exitcode). "fork" and "forkserver" exit the child via os._exit(code), respectively in multiprocessing.popen_fork.Popen._launch and multiprocessing.forkserver.main.

In 3.4+ it works correctly with the "spawn" start method. This uses multiprocessing.spawn.spawn_main, which exits the child via sys.exit(exitcode). "fork" and "forkserver" exit the child via os._exit(code), respectively in multiprocessing.popen_fork.Popen._launch and multiprocessing.forkserver.main.

History
Date	User	Action	Args
2016-07-13 20:30:59	eryksun	set	recipients: + eryksun, tim.peters, pitrou, pietvo, neologix, sbt
2016-07-13 20:30:59	eryksun	set	messageid: <[email protected]>
2016-07-13 20:30:59	eryksun	link	issue18966 messages
2016-07-13 20:30:59	eryksun	create