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 gregory.p.smith
Recipients gregory.p.smith, pitrou
Date 2009-10-16.00:24:03
SpamBayes Score 2.5321e-06
Marked as misclassified No
Message-id <>
In-reply-to <>
> Antoine Pitrou <> added the comment:
> Rather than having a kind of global module registry, locks could keep
> track of what was the last PID, and reinitialize themselves if it changed.
> This is assuming getpid() is fast :-)

Locks can't blindly release themselves because they find themselves
running in another process.

If anything if a lock is held and finds itself running in a new
process any attempt to use the lock should raise an exception so that
the bug is noticed.

I'm not sure a PID check is good enough.  old linux using linuxthreads
had a different pid for every thread, current linux with NPTL is more
like other oses with the same pid for all threads.
Date User Action Args
2009-10-16 00:24:09gregory.p.smithsetrecipients: + gregory.p.smith, pitrou
2009-10-16 00:24:04gregory.p.smithlinkissue6721 messages
2009-10-16 00:24:03gregory.p.smithcreate