Skip to content

gh-96098: Clearly link concurrent.futures from threading & multiprocessing docs #96112

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

Conversation

ncoghlan
Copy link
Contributor

@ncoghlan ncoghlan commented Aug 19, 2022

Also link directly to asyncio from the beginning of the threading docs.

…iprocessing docs

Also link directly to asyncio from the beginning of the threading docs.
@bedevere-bot bedevere-bot added docs Documentation in the Doc dir awaiting core review labels Aug 19, 2022
@ncoghlan
Copy link
Contributor Author

ncoghlan commented Aug 19, 2022

@ADGEfficiency , this docs update was inspired by your tutorial, so I'd be very interested if you think this change would have made the concurrent.futures executor APIs easier to discover.

@ncoghlan ncoghlan added 3.11 only security fixes 3.10 only security fixes labels Aug 19, 2022
@ben-denham
Copy link

@ncoghlan Looks good to me, I also liked the wording you used the other day about how concurrent.futures gives you more flexibility in how you wait for and consume results compared to multiprocessing.pool.Pool.

@ncoghlan ncoghlan merged commit bcc4cb0 into python:main Aug 21, 2022
@ncoghlan ncoghlan added needs backport to 3.10 only security fixes needs backport to 3.11 only security fixes labels Aug 21, 2022
@miss-islington
Copy link
Contributor

Thanks @ncoghlan for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

@miss-islington
Copy link
Contributor

Thanks @ncoghlan for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

@bedevere-bot bedevere-bot removed the needs backport to 3.10 only security fixes label Aug 21, 2022
@bedevere-bot
Copy link

GH-96149 is a backport of this pull request to the 3.10 branch.

@bedevere-bot
Copy link

GH-96150 is a backport of this pull request to the 3.11 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.11 only security fixes label Aug 21, 2022
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request 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 pull request 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 added a commit that referenced this pull request 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.
(cherry picked from commit bcc4cb0)

Co-authored-by: Nick Coghlan <ncoghlan@gmail.com>
miss-islington added a commit that referenced this pull request 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.
(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
Labels
3.10 only security fixes 3.11 only security fixes docs Documentation in the Doc dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants