New submission from Orian Zinger <[email protected]>:
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.
----------
messages: 379801
nosy: zingero
priority: normal
severity: normal
status: open
title: Improving KeyError exception
type: enhancement
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue42177>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
