Martin Panter added the comment:
Updated the patch to address an oversight in the new test cases.
I think Issue 6294 is probably the same underlying issue. The patch there could
be used as the basis for a Python 2 patch. My patches here are for Python 3,
and I suspect the code is significantly different in each version, because the
error messages are different.
Comparison (for bikeshedding etc) with the message produced by the “traceback”
module when str() fails:
>>> try:
... raise BrokenStrException("message")
... except BrokenStrException:
... print_exc()
... raise
...
Traceback (most recent call last):
File "<stdin>", line 2, in <module>
BrokenStrException: <unprintable BrokenStrException object>
Traceback (most recent call last):
File "<stdin>", line 2, in <module>
__main__.BrokenStrException: <str() failed>
----------
stage: -> patch review
versions: +Python 3.5, Python 3.6
Added file: http://bugs.python.org/file39670/unraisable-continue.v3.patch
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22836>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
