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-02-08.22:05:57
SpamBayes Score 3.0330166e-10
Marked as misclassified No
Message-id <1328738758.27.0.249013735312.issue13841@psf.upfronthosting.co.za>
In-reply-to
Content
I think the patch makes multiprocessing.util._exit_function() run twice in non-main processes because it is registered with atexit, and is also called in Process._bootstrap().

_exit_function() does the following:

 * terminate active daemon processes;

 * join active non-daemon processes;

 * run finalizers with non-None exit priority and clear finalizer registry.

So calling _exit_function() twice is probably harmless but should perhaps be fixed.

P.S. It also appears that _exit_function() should set the global _exiting to True, since it declares the variable as a global but does not use it.  As a result util.is_exiting() always returns False.
History
Date User Action Args
2012-02-08 22:05:58sbtsetrecipients: + sbt, pitrou, jnoller, neologix, brandjon
2012-02-08 22:05:58sbtsetmessageid: <1328738758.27.0.249013735312.issue13841@psf.upfronthosting.co.za>
2012-02-08 22:05:57sbtlinkissue13841 messages
2012-02-08 22:05:57sbtcreate