Nick Coghlan <ncogh...@gmail.com> added the comment:
I've thought of a different approach to this which should be less hazardous to
doctests: include the truncation warning in the *traceback* section, rather
than in the header. doctests already ignore the details of that section because
checking it is too fragile.
cc'ing Georg because I think this a potentially big win for the usability of
chained tracebacks, but also think it is dubious from a feature vs fix point of
view.
With the change I'm considering, truncated tracebacks would look something like:
Traceback (most recent call last):
<truncated: another exception occurred>
File "/home/rdmurray/python/email6/Lib/email/message.py", line 466, in
__getattr__
return getattr(self._headers, key)
AttributeError: '_Header_List' object has no attribute 'header_factory'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/rdmurray/python/email6/Lib/mailbox.py", line 1631, in set_flags
self.replace_header('Status', status_flags)
File "/home/rdmurray/python/email6/Lib/email/message.py", line 495, in
replace_header
print('rep', self.header_factory)
File "/home/rdmurray/python/email6/Lib/email/message.py", line 469, in
__getattr__
self.__class__.__name__, key))
AttributeError: 'mboxMessage' object has no attribute 'header_factory'
----------
nosy: +georg.brandl
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12535>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
