Message 151936 - 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	neologix
Recipients	brandjon, jnoller, neologix, pitrou, sbt
Date	2012-01-25.08:30:36
SpamBayes Score	4.835788e-05
Marked as misclassified	No
Message-id	<CAH_1eM3KVyjYawzOgJaM7q1abA=oXshWLcaHQU2O00TVbuBkZA@mail.gmail.com>
In-reply-to	<1327405778.02.0.881326717424.issue13841@psf.upfronthosting.co.za>

Content
> * atexit callbacks are NOT run (although multiprocessing.util._exit_function IS run), It may be a good thing after a fork() (e.g. you don't want to remove the same file twice), but it most definitely looks wrong for a new interpreter process (à la Windows / fork() + exec()). > * the main thread does NOT wait for non-daemonic background threads. Same thing here.

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

It may be a good thing after a fork() (e.g. you don't want to remove
the same file twice), but it most definitely looks wrong for a new
interpreter process (à la Windows / fork() + exec()).

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

Same thing here.

History
Date	User	Action	Args
2012-01-25 08:30:38	neologix	set	recipients: + neologix, pitrou, jnoller, sbt, brandjon
2012-01-25 08:30:37	neologix	link	issue13841 messages
2012-01-25 08:30:36	neologix	create