Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork34.2k
gh-141617: clarifyconcurrent.futures.ThreadPoolExecutor deadlock example#141620
gh-141617: clarifyconcurrent.futures.ThreadPoolExecutor deadlock example#141620picnixz merged 7 commits intopython:mainfrom
concurrent.futures.ThreadPoolExecutor deadlock example#141620Conversation
picnixz left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
The other place where to add the comment was afterb = executor.submit(wait_on_a) just a few lines above not in the documentation forsubmit.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Yashp002 commentedDec 2, 2025
I have made the requested changes; please review again |
Thanks for making the requested changes! @picnixz: please review the changes made to this pull request. |
Yashp002 commentedDec 9, 2025
Hi@picnixz Just checking in on this PR. I'm happy to address any remaining feedback or make changes as needed. Please let me know if there's anything I should update. Thanks. |
Uh oh!
There was an error while loading.Please reload this page.
picnixz left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Keep the blank lines where they are.
concurrent.futures.ThreadPoolExecutorconcurrent.futures.ThreadPoolExecutorconcurrent.futures.ThreadPoolExecutor deadlock exampleYashp002 commentedMar 9, 2026
@picnixz is this PR done then? |
picnixz commentedMar 9, 2026
Hum, it should have been. Looks like the CI failed for some reaason, let me rerun it |
171133a intopython:mainUh oh!
There was an error while loading.Please reload this page.
…lock example (pythonGH-141620)---------(cherry picked from commit 171133aa84cd2fa8738bdbb0c76435645810e8d3)Co-authored-by: Yashraj <yashrajpala8@gmail.com>Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…lock example (pythonGH-141620)---------(cherry picked from commit171133a)Co-authored-by: Yashraj <yashrajpala8@gmail.com>Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
GH-145686 is a backport of this pull request to the3.14 branch. |
GH-145687 is a backport of this pull request to the3.13 branch. |
Uh oh!
There was an error while loading.Please reload this page.
This PR fixes an incomplete code example in the concurrent.futures documentation.
The second example in the deadlock section was missing a
.result()call on the executor.submit() invocation, which is necessary to demonstrate the deadlock behavior described in the comment.Changes:
.result()call to complete the example in Doc/library/concurrent.futures.rstFixes#141617
📚 Documentation preview 📚:https://cpython-previews--141620.org.readthedocs.build/