gh-141617: clarify concurrent.futures.ThreadPoolExecutor deadlock example#141620
gh-141617: clarify concurrent.futures.ThreadPoolExecutor deadlock example#141620Yashp002 wants to merge 6 commits intopython:mainfrom
concurrent.futures.ThreadPoolExecutor deadlock example#141620Conversation
picnixz
left a comment
There was a problem hiding this comment.
The other place where to add the comment was after b = executor.submit(wait_on_a) just a few lines above not in the documentation for submit.
|
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 |
|
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. |
|
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. |
picnixz
left a comment
There was a problem hiding this comment.
Keep the blank lines where they are.
concurrent.futures.ThreadPoolExecutor
concurrent.futures.ThreadPoolExecutorconcurrent.futures.ThreadPoolExecutor deadlock example
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/