Repository navigation
Document asyncio.futures.wrap_future() #68973
Description
| BPO | 24785 |
|---|---|
| Nosy | @agronholm, @berkerpeksag, @1st1 |
| Superseder |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2015-08-03.12:04:02.863>
created_at = <Date 2015-08-03.11:44:43.192>
labels = ['type-feature', 'docs']
title = 'Document asyncio.futures.wrap_future()'
updated_at = <Date 2015-08-03.12:31:27.517>
user = 'https://github.com/agronholm'bugs.python.org fields:
activity = <Date 2015-08-03.12:31:27.517>
actor = 'yselivanov'
assignee = 'docs@python'
closed = True
closed_date = <Date 2015-08-03.12:04:02.863>
closer = 'berker.peksag'
components = ['Documentation']
creation = <Date 2015-08-03.11:44:43.192>
creator = 'alex.gronholm'
dependencies = []
files = []
hgrepos = []
issue_num = 24785
keywords = []
message_count = 2.0
messages = ['247924', '247926']
nosy_count = 4.0
nosy_names = ['alex.gronholm', 'docs@python', 'berker.peksag', 'yselivanov']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '24755'
type = 'enhancement'
url = 'https://bugs.python.org/issue24785'
versions = ['Python 3.5']
Activity
agronholm commentedon Aug 3, 2015
Since Python 3.5 will not support awaiting for concurrent.futures.Futures natively, one has to use the asyncio.futures.wrap_future() function in coroutines like this:
The wrap_future() function is, however, not mentioned in the asyncio documentation. It should be, in order for the standard library to provide the above crutch until proper support arrives in 3.6.
berkerpeksag commentedon Aug 3, 2015
This is a duplicate of bpo-24755.