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 | Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, jnoller, mikemccand, pitrou, tzot |
| Date | 2008年07月12日.21:22:01 |
| SpamBayes Score | 0.01965912 |
| Marked as misclassified | No |
| Message-id | <1215897722.34.0.218653640274.issue874900@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The existing fork-and-thread4.patch doesn't actually reset _active_limbo_lock. Its missing a "global _active_limbo_lock" statement in the threading._after_fork() function. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月12日 21:22:04 | gregory.p.smith | set | spambayes_score: 0.0196591 -> 0.01965912 recipients: + gregory.p.smith, mikemccand, tzot, amaury.forgeotdarc, Rhamphoryncus, pitrou, jnoller |
| 2008年07月12日 21:22:02 | gregory.p.smith | set | spambayes_score: 0.0196591 -> 0.0196591 messageid: <1215897722.34.0.218653640274.issue874900@psf.upfronthosting.co.za> |
| 2008年07月12日 21:22:01 | gregory.p.smith | link | issue874900 messages |
| 2008年07月12日 21:22:01 | gregory.p.smith | create | |