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 | Chris.Farrow, Patrik Dufresne, bquinlan, davin, mark.dickinson, pitrou, simon.jagoe |
| Date | 2017年09月02日.18:16:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1504376213.73.0.412511492932.issue21009@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't really understand this issue. How is concurrent.futures supposed to be the culprit here? Can you elaborate which weakref callback you are talking about? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年09月02日 18:16:53 | pitrou | set | recipients: + pitrou, bquinlan, mark.dickinson, simon.jagoe, Chris.Farrow, davin, Patrik Dufresne |
| 2017年09月02日 18:16:53 | pitrou | set | messageid: <1504376213.73.0.412511492932.issue21009@psf.upfronthosting.co.za> |
| 2017年09月02日 18:16:53 | pitrou | link | issue21009 messages |
| 2017年09月02日 18:16:53 | pitrou | create | |