[issue28603] traceback module can't format/print unhashable exceptions

Serhiy Storchaka added the comment: Thank you for your contribution Zane. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5 ___ Python tracker

[issue28603] traceback module can't format/print unhashable exceptions

Serhiy Storchaka added the comment: New changeset 2712247ec94dcc12cf9abeec78f18f54fcc3357a by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.6] bpo-28603: Fix formatting tracebacks for unhashable exceptions (GH-4014) (#4024) https://github.com/python/cpython/commit/2712247ec94dcc

[issue28603] traceback module can't format/print unhashable exceptions

Change by Roundup Robot : -- pull_requests: +3999 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28603] traceback module can't format/print unhashable exceptions

Serhiy Storchaka added the comment: New changeset de86073a761cd3539aaca6f886a1f55effc0d9da by Serhiy Storchaka (Zane Bitter) in branch 'master': bpo-28603: Fix formatting tracebacks for unhashable exceptions (#4014) https://github.com/python/cpython/commit/de86073a761cd3539aaca6f886a1f55effc0d

[issue28603] traceback module can't format/print unhashable exceptions

Terry J. Reedy added the comment: As I understand it, the patch amounts to ignoring any custom __eq__ and __hash__ on an Exception class when printing tracebacks and, in effect, using the default id-based versions inherited from object, as is being assumed. This seems right to me in this con

[issue28603] traceback module can't format/print unhashable exceptions

Zane Bitter added the comment: I also encountered this issue, and I'd like to further note that it is extraordinarily difficult to debug without access to stderr. If your logging facility uses the traceback module then it will be unable to record both the original (unhashable) exception, and

[issue28603] traceback module can't format/print unhashable exceptions

Change by Zane Bitter : -- pull_requests: +3988 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue28603] traceback module can't format/print unhashable exceptions

Chris Barth added the comment: There are now several patches for this problem, which also affects me. What are the next steps to get this resolved? -- ___ Python tracker ___ ___

[issue28603] traceback module can't format/print unhashable exceptions

Changes by Chris Barth : -- nosy: +Chris Barth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue28603] traceback module can't format/print unhashable exceptions

Serhiy Storchaka added the comment: There is no issue28603-listset.patch. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python

[issue28603] traceback module can't format/print unhashable exceptions

Changes by Jelle Zijlstra : Added file: http://bugs.python.org/file45872/issue28603-list.patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue28603] traceback module can't format/print unhashable exceptions

Jelle Zijlstra added the comment: I ran into this bug through Thrift-generated exception classes (also reported there as https://issues.apache.org/jira/browse/THRIFT-4002). I've added a few potential solutions: - issue28603-listset.patch turns the seen set into a list if hashing fails. However

[issue28603] traceback module can't format/print unhashable exceptions

Changes by Jelle Zijlstra : Added file: http://bugs.python.org/file45871/issue28603-ignore.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue28603] traceback module can't format/print unhashable exceptions

Andreas Stührk added the comment: It was reported as bug to a project that uses the traceback module (https://github.com/bpython/bpython/issues/651). Parsley (https://pypi.python.org/pypi/Parsley) is at least one library that uses unhashable exceptions, although I guess it's by accident: it de

[issue28603] traceback module can't format/print unhashable exceptions

Berker Peksag added the comment: Thanks for the patch. Out of curiosity, how did you get an unhashable exception? Is there a way to reproduce this without creating a custom exception and set __hash__ to None? In other words, what's your use case? -- nosy: +berker.peksag stage: -> patc

[issue28603] traceback module can't format/print unhashable exceptions

New submission from Andreas Stührk: The traceback module tries to handle loops caused by an exception's __cause__ or __context__ attributes when printing tracebacks. To do so, it adds already seen exceptions to a set. Unfortunately, it doesn't handle unhashable exceptions: >>> class E(Excepti