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 asksol, brandon-rhodes, cool-RR, dholth, jnoller, neologix, numbernine, pitrou, rcoyner, santoso.wijaya, sbt, vsekhar
Date 2011-12-21.15:57:23
SpamBayes Score 4.490852e-14
Marked as misclassified No
Message-id <>
> I think this is indeed useful, but I'm tempted to go further and say we 
> should make this the default - and only - behavior. This will probably 
> break existing code that accidentaly relied the fact that the 
> implementation uses a bare fork(), but i'd say it's worth it:

I'm not convinced about making it the default behaviour, and certainly not the only one.

I have a working patch which ensures that leaked semaphores get cleaned up on exit.  However, I think to add proper tests for the patch, test_multiprocessing needs to be refactored.  Maybe we could end up with

The actual unittests would be in and  The other files would run the unittests in using different configurations.

Date User Action Args
2011-12-21 15:57:24sbtsetrecipients: + sbt, pitrou, jnoller, rcoyner, asksol, cool-RR, dholth, brandon-rhodes, neologix, santoso.wijaya, numbernine, vsekhar
2011-12-21 15:57:24sbtsetmessageid: <>
2011-12-21 15:57:24sbtlinkissue8713 messages
2011-12-21 15:57:23sbtcreate