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 zingero
Date 2020-10-27.20:43:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603831389.37.0.739931289382.issue42177@roundup.psfhosted.org>
In-reply-to
Content
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.

https://github.com/zingero/cpython/commit/8c9e5d9e16296cee1f3ec05638dd6989dae8b811

Regards,
Orian.
History
Date User Action Args
2020-10-27 20:43:09zingerosetrecipients: + zingero
2020-10-27 20:43:09zingerosetmessageid: <1603831389.37.0.739931289382.issue42177@roundup.psfhosted.org>
2020-10-27 20:43:09zingerolinkissue42177 messages
2020-10-27 20:43:09zingerocreate