Closed mardukbp closed 1 year ago
Thank you for reporting this. It is fixed now. The problem occurred as I made some changes to friendly_traceback including adding support for exception notes (new in Python 3.11), and did not tested friendly thoroughly as you pointed out. Whenever major changes are made in friendly_traceback, I hurry to upload a new version of friendly to make sure friendly does not raise exceptions due to the new features ... and missed this completelly. I completely agree that friendly should NEVER generate unfriendly stack traces.
I have uploaded a new version of both friendly and friendly_traceback. I will leave this issue open until I introduce some tests for friendly.
Thank you for fixing it so quickly! I already recommended friendly to a friend. And will continue to spread the word :)
Since version 0.7.12, whenever a Python exception occurs friendly fails with a KeyError:
I reproduced the above with Python 3.6, 3.8 and 3.10 on Windows and Python 3.10 on Ubuntu.
I believe uploading every day a patch version to pypi is a bad idea. It is better to test thoroughly before releasing a new version.
Please remove all releases after 0.7.11 from pypi. Installing friendly should just work and not generate unfriendly stack traces ;)