[3.9] bpo-42669: Document that except
rejects nested tuples (GH-23822)
#23870
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.
In Python 2, it was possible to use
except
with a nested tuple, and occasionally natural. For example,zope.formlib.interfaces.InputErrors
is a tuple of several exception classes, and one might reasonably think to do something like this:As of Python 3.0, this raises
TypeError: catching classes that do not inherit from BaseException is not allowed
instead: one must instead either break it up into multipleexcept
clauses or flatten the tuple. However, the reference documentation was never updated to match this new restriction. Make it clear that the definition is no longer recursive.Automerge-Triggered-By: GH:ericvsmith
(cherry picked from commit c95f8bc)
Co-authored-by: Colin Watson cjwatson@debian.org
https://bugs.python.org/issue42669