Message279579
> Why isfuture() is moved, and asyncio.coroutine uses > base_futures.isfuture() instead of futures.isfuture()? Import cycles: - `_asyncio` module is now being imported from `futures.py` - and `_asyncio` is now imported from `tasks.py`; - and `tasks.py` imports `futures.py` to have `isfuture`. Long story short, I don't see a way of keeping `isfuture` in `futures.py`. The easiest option is to have it in a separate module. | |
| Date | User | Action | Args | | 2016-10-28 04:23:10 | yselivanov | set | recipients: + yselivanov, gvanrossum, vstinner, ned.deily, asvetlov, methane, Elvis.Pranskevichus | | 2016-10-28 04:23:10 | yselivanov | set | messageid: <1477628590.1.0.526163735497.issue28544@psf.upfronthosting.co.za> | | 2016-10-28 04:23:10 | yselivanov | link | issue28544 messages | | 2016-10-28 04:23:09 | yselivanov | create | | |