Message197215
| Author |
tim.peters |
| Recipients |
Tamas.K, bkabrda, csernazs, grahamd, jcea, ncoghlan, neologix, pitrou, python-dev, tim.peters |
| Date |
2013年09月08日.02:51:18 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1378608679.24.0.379120697112.issue18808@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Doesn't look like 5cfd7b2eb994 is going to fix it :-( So I'll revert it. Attaching the patch as blind.patch. After that patch, is_alive() only looks at Thread data members, where ._is_stopped "is obviously" True, and ._tstate_lock "is obviously" None, both forced by threading.py's _after_fork() function. No theory as to how that can be screwed up. |
|