➜
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.
Created on 2010-07-23 11:19 by bbrazil, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| threading-roughly-doc-fix.patch | bbrazil, 2010-07-23 11:30 | Clarification of threading is_alive docs. | ||
| Messages (3) | |||
|---|---|---|---|
| msg111278 - (view) | Author: Brian Brazil (bbrazil) * | Date: 2010-07-23 11:19 | |
http://docs.python.org/py3k/library/threading.html "Roughly, a thread is alive from the moment the start() method returns until its run() method terminates." Using "Roughly" in relation to threading is a bit unspecific. I've had a look through _bootstrap_inner() and attached a patch to clarify this. |
|||
| msg111281 - (view) | Author: Brian Brazil (bbrazil) * | Date: 2010-07-23 11:30 | |
Here's a slightly cleaner version. |
|||
| msg111296 - (view) | Author: Brett Cannon (brett.cannon) *  |
Date: 2010-07-23 12:30 | |
3.2: 83080 3.1: 83081 2.7: 83082 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:04 | admin | set | github: 53585 |
| 2010-07-23 12:30:36 | brett.cannon | set | status: open -> closed nosy: + brett.cannon messages: + msg111296 resolution: fixed |
| 2010-07-23 11:30:28 | bbrazil | set | files:
+ threading-roughly-doc-fix.patch messages: + msg111281 |
| 2010-07-23 11:29:52 | bbrazil | set | files: - threading-roughly-doc-fix.patch |
| 2010-07-23 11:19:27 | bbrazil | create | |