clarify concurrent.futures docs to not refer to async Futures except where truly necessary

[applio]

BPO	28052
Nosy	@applio

^{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 = None
created_at = <Date 2016-09-09.20:08:22.494>
labels = ['type-feature']
title = 'clarify concurrent.futures docs to not refer to async Futures except where truly necessary'
updated_at = <Date 2016-09-09.20:08:22.494>
user = 'https://github.com/applio'

bugs.python.org fields:

activity = <Date 2016-09-09.20:08:22.494>
actor = 'davin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2016-09-09.20:08:22.494>
creator = 'davin'
dependencies = []
files = []
hgrepos = []
issue_num = 28052
keywords = []
message_count = 1.0
messages = ['275417']
nosy_count = 1.0
nosy_names = ['davin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue28052'
versions = ['Python 3.5', 'Python 3.6']

Linked PRs

• gh-72239: Add note distinguishing concurrent.futures.Future from asyncio.Future #143288

[applio]

Per discussions with Yury, Lukasz and BDFL.

[aisk]

Hi, I don't see any asyncio.Future related descriptions in this document: https://docs.python.org/3/library/concurrent.futures.html. I think maybe this has already been resolved by other changes in the last 10 years? Or is the issue just about adding a clarification that concurrent.futures doesn't have any relationship with asyncio.Future?

[picnixz]

Actually, there is a clarification the other way around, at the bottom of https://docs.python.org/3/library/asyncio-future.html#future-object. We could add a small sentence at the beginning of https://docs.python.org/3/library/concurrent.futures.html#future-objects that says "Concurrent's futures must not be confused with asyncio's futures".