This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zingero
Recipients barry, brett.cannon, cvrebert, ezio.melotti, mark.dickinson, r.david.murray, rhettinger, zingero
Date 2020-10-05.20:39:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hi all,

As a Python developer, I encountered lots of blurry exception messages in the product logs such as:
<time and date> <process name> <log severity> Failed to do something. Exception: 'some key'

I believe printing the key name without explaining the exception itself is bad (explicit is better than implicit).

Thus, after forking the repository, I added a short explanation about the Exception.
Now, it looks like:

>>> try:
...     {}['some key']
... except Exception as e:
...     print(e)
Missing key: some key

I'm a newbie in a contribution to CPython, so please let me know if the idea behind my commit is good. If not, please explain how can I improve my commit so it'll be pulled later to the main branch.

Date User Action Args
2020-10-05 20:39:11zingerosetrecipients: + zingero, barry, brett.cannon, rhettinger, mark.dickinson, ezio.melotti, r.david.murray, cvrebert
2020-10-05 20:39:11zingerosetmessageid: <>
2020-10-05 20:39:11zingerolinkissue18163 messages
2020-10-05 20:39:10zingerocreate