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.

Title: asyncio.isfuture() should support Mocks
Type: behavior Stage: resolved
Components: asyncio Versions: Python 3.7, Python 3.6, Python 3.5
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: yselivanov Nosy List: gvanrossum, python-dev, yselivanov
Priority: normal Keywords:

Created on 2016-11-07 21:00 by yselivanov, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg280241 - (view) Author: Yury Selivanov (yselivanov) * (Python committer) Date: 2016-11-07 21:00
In short:

isfuture(unittest.mock.Mock()) should be False
isfuture(unittest.mock.Mock(Future)) should be True

This issue is a proxy for
msg280242 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2016-11-07 21:08
New changeset 0669dcf1eb36 by Yury Selivanov in branch '3.5':
Issue #28634: Fix asyncio.isfuture() to support mocks

New changeset a02915e4c165 by Yury Selivanov in branch '3.6':
Merge 3.5 (issue #28634)

New changeset 44c1ec7689e5 by Yury Selivanov in branch 'default':
Merge 3.6 (issue #28634)
Date User Action Args
2022-04-11 14:58:39adminsetgithub: 72820
2016-11-07 21:08:05python-devsetnosy: + python-dev
messages: + msg280242
2016-11-07 21:00:31yselivanovsetstatus: open -> closed
resolution: fixed
2016-11-07 21:00:19yselivanovcreate