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 neologix
Recipients emptysquare, gregory.p.smith, neologix, sbt
Date 2013-07-15.20:30:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0p7h-d9y4bW1PxjovW3tjb32LxQsX1g_ySVxh2XiirjA@mail.gmail.com>
In-reply-to <1373915757.43.0.66332938347.issue18418@psf.upfronthosting.co.za>
Content
> If you want a consistent reproducible test case for this I believe you will need to replace the Thread object's __started with a test wrapper who's set() method blocks waiting for for the fork to have happened before doing the actual set().  That is a bit tricky and may not be worth it.

Actually, setting sys.setswitchinterval(1e-6) makes it fairly easy to reproduce.
History
Date User Action Args
2013-07-15 20:30:57neologixsetrecipients: + neologix, gregory.p.smith, sbt, emptysquare
2013-07-15 20:30:57neologixlinkissue18418 messages
2013-07-15 20:30:57neologixcreate