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 | martin.panter |
|---|---|
| Recipients | Corbin.Simpson, docs@python, gvanrossum, martin.panter, r.david.murray, vstinner, yselivanov |
| Date | 2014年12月13日.06:53:01 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1418453582.27.0.793612227254.issue22875@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I have been bitten by this when attempting to implement my own event loops. Parts of the "asyncio" code itself expects that the callback is not invoked directly after call_soon() returns. Here is a simple patch. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年12月13日 06:53:02 | martin.panter | set | recipients: + martin.panter, gvanrossum, vstinner, r.david.murray, docs@python, yselivanov, Corbin.Simpson |
| 2014年12月13日 06:53:02 | martin.panter | set | messageid: <1418453582.27.0.793612227254.issue22875@psf.upfronthosting.co.za> |
| 2014年12月13日 06:53:02 | martin.panter | link | issue22875 messages |
| 2014年12月13日 06:53:02 | martin.panter | create | |