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 | Tamas.K, csernazs, grahamd, jcea, ncoghlan, neologix, pitrou, python-dev, tim.peters |
| Date | 2013年09月07日.18:59:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1378580364.86.0.402305781856.issue18808@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Anyone doing a join() with a timeout has to be aware that they have no > idea whether the thread is done when join() returns, and do another > join() or check is_alive() later. Agreed. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年09月07日 18:59:24 | pitrou | set | recipients: + pitrou, tim.peters, jcea, csernazs, ncoghlan, grahamd, neologix, python-dev, Tamas.K |
| 2013年09月07日 18:59:24 | pitrou | set | messageid: <1378580364.86.0.402305781856.issue18808@psf.upfronthosting.co.za> |
| 2013年09月07日 18:59:24 | pitrou | link | issue18808 messages |
| 2013年09月07日 18:59:24 | pitrou | create | |