diff options
| author | Colin Watson <cjwatson@debian.org> | 2020-12-20 18:24:10 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-12-20 18:24:10 (GMT) |
| commit | c95f8bc2700b42f4568886505a819816c9b0ba28 (patch) | |
| tree | 105ca01ea2f7d4b5603135d8a3ec30d354335b98 /Python/sysmodule.c | |
| parent | b0398a4b7fb5743f6dbb72ac6b2926e0a0c11498 (diff) | |
| download | cpython-c95f8bc2700b42f4568886505a819816c9b0ba28.zip cpython-c95f8bc2700b42f4568886505a819816c9b0ba28.tar.gz cpython-c95f8bc2700b42f4568886505a819816c9b0ba28.tar.bz2 | |
bpo-42669: Document that `except` rejects nested tuples (GH-23822)
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:
try:
self.getInputValue()
return True
except (InputErrors, SomethingElse):
return False
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 multiple `except` 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
Diffstat (limited to 'Python/sysmodule.c')
0 files changed, 0 insertions, 0 deletions
