Message 352362 - 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	davin
Recipients	chrahunt, davin, eamanu
Date	2019-09-13.16:41:20
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1568392880.14.0.0579567388548.issue35727@roundup.psfhosted.org>
In-reply-to

Content
I believe the mentality behind multiprocessing.Process triggering an exit code of 1 when sys.exit() is invoked inside its process is to indicate a non-standard exit out of its execution. There may yet be other side effects that could be triggered by having a sys.exit(0) translate into an exit code of 0 from the Process's process -- and we might not notice them with the current tests. Was there a particular use case that motivates this suggested change?

I believe the mentality behind multiprocessing.Process triggering an exit code of 1 when sys.exit() is invoked inside its process is to indicate a non-standard exit out of its execution.  There may yet be other side effects that could be triggered by having a sys.exit(0) translate into an exit code of 0 from the Process's process -- and we might not notice them with the current tests.

Was there a particular use case that motivates this suggested change?

History
Date	User	Action	Args
2019-09-13 16:41:20	davin	set	recipients: + davin, eamanu, chrahunt
2019-09-13 16:41:20	davin	set	messageid: <1568392880.14.0.0579567388548.issue35727@roundup.psfhosted.org>
2019-09-13 16:41:20	davin	link	issue35727 messages
2019-09-13 16:41:20	davin	create