➜

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 pitrou
Recipients belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, neologix, pitrou, vstinner
Date 2012-04-29.00:54:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335660911.18.0.518383478117.issue9260@psf.upfronthosting.co.za>
In-reply-to
Content 
Updated patch fixes the performance issue and disposes of module locks when they aren't used anymore.
Only the afterfork question remains. Should I hook in threading's own facility? Should we wait for an atfork module? Something else.
History
Date User Action Args
2012-04-29 00:55:12pitrousetrecipients: + pitrou, gvanrossum, brett.cannon, ncoghlan, belopolsky, vstinner, christian.heimes, grahamd, neologix
2012-04-29 00:55:11pitrousetmessageid: <1335660911.18.0.518383478117.issue9260@psf.upfronthosting.co.za>
2012-04-29 00:55:10pitroulinkissue9260 messages
2012-04-29 00:55:10pitroucreate