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 | jyasskin |
|---|---|
| Recipients | dripton, jyasskin, schmir |
| Date | 2008年02月28日.18:23:08 |
| SpamBayes Score | 0.006124158 |
| Marked as misclassified | No |
| Message-id | <1204222989.43.0.686965182683.issue1183@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hmm. I think the race can only happen if you call collect_children() concurrently from multiple threads or from a signal handler. The waidpid(0) bug (which affected anyone who spawned subprocesses from anything other than ForkingMixIn) is partly fixed by r61106, but I don't intend to make ForkingMixIn thread- or signal-safe. Let me know if this is enough for you. :) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月28日 18:23:09 | jyasskin | set | spambayes_score: 0.00612416 -> 0.006124158 recipients: + jyasskin, dripton, schmir |
| 2008年02月28日 18:23:09 | jyasskin | set | spambayes_score: 0.00612416 -> 0.00612416 messageid: <1204222989.43.0.686965182683.issue1183@psf.upfronthosting.co.za> |
| 2008年02月28日 18:23:08 | jyasskin | link | issue1183 messages |
| 2008年02月28日 18:23:08 | jyasskin | create | |