Skip to content
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.

Sign up for GitHub

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

PEP-654: state in rationale the premise that the new features will be… #1851

Merged
merged 1 commit into from
Mar 1, 2021
Merged

PEP-654: state in rationale the premise that the new features will be… #1851

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions pep-0654.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,13 @@ The purpose of this PEP, then, is to add the ``except*`` syntax for handling
handling semantics, so we are not proposing to modify the behavior of the
``except`` keyword but rather to add the new ``except*`` syntax.

Our premise is that ``ExceptionGroups`` and ``except*`` will be used
selectively, only when they are needed. We do not expect them to become
the default mechanism for exception handling. The decision to raise
``ExceptionGroup`` from a library needs to be considered carefully and
regarded as an API-breaking change. We expect that this will normally be
done by introducing a new API rather than modifying an existing one.


Specification
=============
Expand Down