Skip to content

[Pylint Data: bare-except]: Update details.md #80

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
BethanyG merged 1 commit into from
Apr 30, 2026
Merged

[Pylint Data: bare-except]: Update details.md #80

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
2 changes: 1 addition & 1 deletion lib/common/pylint_data/messages/bare-except/details.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,5 @@ A good rule of thumb is to limit use of bare 'except' clauses to two
cases: 1. If the exception handler will be printing out or logging the
traceback; at least the user will be aware that an error has occurred.
2. If the code needs to do some cleanup work, but then lets the
exception propagate upwards with raise. [try\...finally]{.title-ref} can
exception propagate upwards with raise. [`try\...finally`](https://docs.python.org/3/reference/compound_stmts.html#finally-clause) can
be a better way to handle this case.