Message 151896 - 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	sbt
Recipients	brandjon, jnoller, neologix, pitrou, sbt
Date	2012-01-24.11:49:37
SpamBayes Score	0.004305516
Marked as misclassified	No
Message-id	<1327405778.02.0.881326717424.issue13841@psf.upfronthosting.co.za>
In-reply-to

Content
Currently, on both Windows and Unix, when the main thread of a child process exits: * atexit callbacks are NOT run (although multiprocessing.util._exit_function IS run), * the main thread does NOT wait for non-daemonic background threads. A simple replacement of ExitProcess() by sys.exit() would change this. Whether that would be a good thing, I don't know.

Currently, on both Windows and Unix, when the main thread of a child process exits:

* atexit callbacks are NOT run (although multiprocessing.util._exit_function IS run),

* the main thread does NOT wait for non-daemonic background threads.

A simple replacement of ExitProcess() by sys.exit() would change this.  Whether that would be a good thing, I don't know.

History
Date	User	Action	Args
2012-01-24 11:49:38	sbt	set	recipients: + sbt, pitrou, jnoller, neologix, brandjon
2012-01-24 11:49:38	sbt	set	messageid: <1327405778.02.0.881326717424.issue13841@psf.upfronthosting.co.za>
2012-01-24 11:49:37	sbt	link	issue13841 messages
2012-01-24 11:49:37	sbt	create