-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-43293: Doc: move note about GIL to top of threading module #24622
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
The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility.
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Thanks @quantum5 for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Thanks @quantum5 for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Thanks @quantum5 for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
GH-24640 is a backport of this pull request to the 3.9 branch. |
Sorry, @quantum5 and @pablogsal, I could not cleanly backport this to |
Sorry @quantum5 and @pablogsal, I had trouble checking out the |
…nGH-24622) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
Thanks @quantum5 for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Thanks @quantum5 for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
GH-24641 is a backport of this pull request to the 3.8 branch. |
Sorry, @quantum5 and @pablogsal, I could not cleanly backport this to |
…nGH-24622) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
@quantum5 could you do the manual backport to 3.7? |
) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
…ythonGH-24622) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility.. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
GH-24642 is a backport of this pull request to the 3.7 branch. |
@pablogsal I manually backported this to the 3.7 branch. Can you approve and merge the pull request? |
Done 👍 Thanks a lot |
…H-24622) (#24642) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility.. (cherry picked from commit 32181be) Co-authored-by: Guanzhong Chen <[email protected]>
…nGH-24622) The note about the GIL was buried pretty deep in the threading documentation, and this made it hard for first time users to discover why their attempts at using threading to parallelizing their application did not work. In this commit, the note is moved to the top of the module documention for visibility.
The note about the GIL was buried pretty deep in the threading documentation,
and this made it hard for first time users to discover why their attempts
at using threading to parallelize their application did not work.
In this commit, the note is moved to the top of the module documention for
visibility.
https://bugs.python.org/issue43293