-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote concurrent.futures in threading and multiprocessing docs #96098
Labels
docs
Documentation in the Doc dir
Comments
ncoghlan
added a commit
to ncoghlan/cpython
that referenced
this issue
Aug 19, 2022
…iprocessing docs Also link directly to asyncio from the beginning of the threading docs.
ncoghlan
added a commit
that referenced
this issue
Aug 21, 2022
…ssing docs (GH-96112) Clearly link concurrent.futures from threading & multiprocessing docs Also link directly to asyncio from the beginning of the threading docs.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Aug 21, 2022
…iprocessing docs (pythonGH-96112) Clearly link concurrent.futures from threading & multiprocessing docs Also link directly to asyncio from the beginning of the threading docs. (cherry picked from commit bcc4cb0) Co-authored-by: Nick Coghlan <ncoghlan@gmail.com>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Aug 21, 2022
…iprocessing docs (pythonGH-96112) Clearly link concurrent.futures from threading & multiprocessing docs Also link directly to asyncio from the beginning of the threading docs. (cherry picked from commit bcc4cb0) Co-authored-by: Nick Coghlan <ncoghlan@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Documentation
Attending a tutorial on distributed computation at KiwiPyCon, it struck me that the concurrent.futures module wasn't even mentioned, even though it is a better option than using the threading or multiprocessing modules directly for local IO bound or CPU bound operations (see https://peps.python.org/pep-3148/ for background).
Reviewing the docs, one notable omission is that neither of the lower level modules provides an explicit pointer to the higher level interface. The only cross-references are:
It would make sense to provide pointers early in the low level docs for cases where the high level API is more appropriate
The text was updated successfully, but these errors were encountered: