Yury Selivanov added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28544> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
