When using a bare except in a python exercise (and getting “[W0702 bare-except]”), the analyzer’s feedback appears to contain unparsed markdown for links:
Screenshot transcript
- [Programming recommendation in PEP8](https://peps.python.org/pep-0008/#programming-recommendations)
- [PEP 760 – No More Bare Excepts (Rejected)](https://peps.python.org/pep-0760/)
- [Discussion about PEP 760](https://discuss.python.org/t/pep-760-no-more-bare-excepts/67182)
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 be a better way to handle this case.
In addition to the links, it also has “[try...finally]{.title-ref}” which seems like another unparsed statement, but it doesn’t look like markdown (though it might just be a syntax I’m unaware of).
