gh-140920: remove incorrect mentions to concurrent.futures.interpreter.ExecutionFailed#141723
Merged
picnixz merged 2 commits intopython:mainfrom Dec 31, 2025
Merged
Conversation
bedevere-app
bot
added
awaiting review
docs
picnixz
reviewed
Nov 18, 2025
Member
picnixz
left a comment
picnixz
left a comment
There was a problem hiding this comment.
Please also remove .. exception:: ExecutionFailed at the very end of the document as that exception doesn't exist in concurrent.futures.
picnixz
approved these changes
Dec 31, 2025
picnixz
changed the title
concurrent.futures.interpreter.ExecutionFailed
|
Thanks @Lakshya-Upadhyaya for the PR, and @picnixz for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Dec 31, 2025
…erpreter.ExecutionFailed` (pythonGH-141723) Remove documentation for inexistant `concurrent.futures.interpreter.ExecutionFailed` and replace its occurrences by `concurrent.interpreters.ExecutionFailed` since this is the documented exception. (cherry picked from commit c521597) Co-authored-by: Lakshya Upadhyaya <lakshya.upadhyaya05@gmail.com>
|
GH-143315 is a backport of this pull request to the 3.14 branch. |
picnixz
pushed a commit
that referenced
this pull request
Dec 31, 2025
…terpreter.ExecutionFailed` (GH-141723) (#143315) gh-140920: remove incorrect mentions to `concurrent.futures.interpreter.ExecutionFailed` (GH-141723) Remove documentation for inexistant `concurrent.futures.interpreter.ExecutionFailed` and replace its occurrences by `concurrent.interpreters.ExecutionFailed` since this is the documented exception. (cherry picked from commit c521597) Co-authored-by: Lakshya Upadhyaya <lakshya.upadhyaya05@gmail.com>
thunder-coding
pushed a commit
to thunder-coding/cpython
that referenced
this pull request
Feb 15, 2026
…erpreter.ExecutionFailed` (python#141723) Remove documentation for inexistant `concurrent.futures.interpreter.ExecutionFailed` and replace its occurrences by `concurrent.interpreters.ExecutionFailed` since this is the documented exception.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documentation incorrectly referenced
concurrent.futures.interpreter.ExecutionFailed,an exception that does not exist. The actual
ExecutionFailedclass is defined inconcurrent.interpreters.This patch updates the concurrent.futures documentation to point to the correct
exception class.
concurrent.futures.interpreter.ExecutionFaileddocumentation #140920📚 Documentation preview 📚: https://cpython-previews--141723.org.readthedocs.build/