From 499d0fb538fac4ac2c08cde16ebe1415ab9aa68d Mon Sep 17 00:00:00 2001 From: BethanyG Date: Thu, 30 Apr 2026 12:18:44 -0700 Subject: [PATCH] [Pylint Data: bare-except]: Update details.md Fixed broken ref to try\...finally. --- lib/common/pylint_data/messages/bare-except/details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/common/pylint_data/messages/bare-except/details.md b/lib/common/pylint_data/messages/bare-except/details.md index ef49eaa..ada39f5 100644 --- a/lib/common/pylint_data/messages/bare-except/details.md +++ b/lib/common/pylint_data/messages/bare-except/details.md @@ -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.