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 nadeem.vawda, neologix, pitrou, sbt
Date 2012-04-11.23:07:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334185656.37.0.476304514318.issue14548@psf.upfronthosting.co.za>
In-reply-to
Content
> That's a problem indeed. Perhaps we need a global "fork lock" shared
> between subprocess and multiprocessing?

I did an atfork patch which included a (recursive) fork lock.  See

    http://bugs.python.org/review/6721/show

The patch included changes to multiprocessing and subprocess.  (Being able to acquire the lock when doing fd manipulation is quite useful.  For instance, the creation of Process.sentinel currently has a race which can mean than another process inherits the write end of the pipe.  That would cause Process.join() to wait till both processes terminate.)

Actually, for Finalizers I think it would be easier to just record and check the pid.
History
Date User Action Args
2012-04-11 23:07:36sbtsetrecipients: + sbt, pitrou, nadeem.vawda, neologix
2012-04-11 23:07:36sbtsetmessageid: <1334185656.37.0.476304514318.issue14548@psf.upfronthosting.co.za>
2012-04-11 23:07:35sbtlinkissue14548 messages
2012-04-11 23:07:35sbtcreate