Message242054
| Author | Ludovic.Gasc |
|---|---|
| Recipients | Ludovic.Gasc, gvanrossum, lukasz.langa, martin.panter, pitrou, rhettinger, scoder, vstinner, yselivanov |
| Date | 2015-04-26.12:58:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1430053121.82.0.847142528534.issue24018@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Sorry guys to be basic for you, but if I take my "AsyncIO end-user" hat, I'm not sure to understand the potential end-user source code impacts to use Cython with Python 3.5 and AsyncIO. In concrete terms, it's only a low-level change, Cython will monkeypatch CPython if it's missing. I can continue to use asyncio.iscoroutine() function to detect coroutines. Or it should be better to change something in AsyncIO libs and/or end-user source code ? With the potential async/await inclusion in Python 3.5, it should be good to know if something else is necessary to help for the Cython support. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-04-26 12:58:41 | Ludovic.Gasc | set | recipients: + Ludovic.Gasc, gvanrossum, rhettinger, pitrou, scoder, vstinner, lukasz.langa, martin.panter, yselivanov |
| 2015-04-26 12:58:41 | Ludovic.Gasc | set | messageid: <1430053121.82.0.847142528534.issue24018@psf.upfronthosting.co.za> |
| 2015-04-26 12:58:41 | Ludovic.Gasc | link | issue24018 messages |
| 2015-04-26 12:58:41 | Ludovic.Gasc | create | |