Skip to content

PEP 249: Replace StandardError with Exception #2781

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

Merged
malemburg merged 6 commits into from
Sep 6, 2022
Merged

PEP 249: Replace StandardError with Exception #2781

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c004fe8
Replace StandardError with Exception to avoid confusion when using
malemburg Sep 2, 2022
67bbfeb
Fix typo and add year for more context.
malemburg Sep 2, 2022
5e5522f
Remove mention of the exceptions module
malemburg Sep 2, 2022
b4c4c3b
Remove mention of exception objects being builtins.
malemburg Sep 2, 2022
c49fdd4
Grammar fix
malemburg Sep 6, 2022
f0bf65b
Fix exception hierarchy formatting
malemburg Sep 6, 2022
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
Prev Previous commit
Next Next commit
Remove mention of exception objects being builtins. 
They were already for a very long time, so this is pointless.
I only had this sentence to explain why I had removed the
"import exceptions" line from the Python 2 days.
  • Loading branch information
@malemburg
malemburg committed Sep 2, 2022
commit b4c4c3bb8c49ba968d77908e5e68966bf888916f
10 changes: 4 additions & 6 deletions pep-0249.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1299,12 +1299,10 @@ Footnotes
was used as the base class for all DB-API exceptions. Since
``StandardError`` was removed in Python 3, database modules
targeting Python 3 should use ``Exception`` as base class instead.
Both ``StandardError`` and ``Exception`` are available as builtin
exception objects. The PEP was updated to use ``Exception``
throughout the text, to avoid confusion. The change should not
affect existing modules or uses of those modules, since all DB-API
error exception classes are still rooted at the ``Error`` or
``Warning`` classes.
The PEP was updated to use ``Exception`` throughout the text, to
avoid confusion. The change should not affect existing modules or
uses of those modules, since all DB-API error exception classes are
still rooted at the ``Error`` or ``Warning`` classes.

.. [11] In a future revision of the DB-API, the base class for
``Warning`` will likely change to the builtin ``Warning`` class. At
Expand Down