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 | Victor.Varvariuc |
|---|---|
| Recipients | Nam.Nguyen, Victor.Varvariuc, bquinlan, r.david.murray |
| Date | 2014年01月07日.08:42:46 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1389084166.64.0.483951119499.issue14119@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Maybe I should have created another issue for this, but without this issue being solved, the new issue will not help much. Here it is: http://hg.python.org/cpython/file/37caaf21f827/Lib/concurrent/futures/thread.py#l63 After running an work item `work_queue.task_done()` is not called. So it's difficult to know if worker threads have any more work to do. http://stackoverflow.com/questions/20965754/determine-if-worker-threads-are-doing-any-work?noredirect=1#comment31495804_20965754 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年01月07日 08:42:46 | Victor.Varvariuc | set | recipients: + Victor.Varvariuc, bquinlan, r.david.murray, Nam.Nguyen |
| 2014年01月07日 08:42:46 | Victor.Varvariuc | set | messageid: <1389084166.64.0.483951119499.issue14119@psf.upfronthosting.co.za> |
| 2014年01月07日 08:42:46 | Victor.Varvariuc | link | issue14119 messages |
| 2014年01月07日 08:42:46 | Victor.Varvariuc | create | |