This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Don't use None as sentinel for traceback
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.4
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: Drekin, benjamin.peterson
Priority: normal Keywords:

Created on 2015-07-23 14:52 by Drekin, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg247210 - (view) Author: Adam Bartoš (Drekin) * Date: 2015-07-23 14:52
There is a subtle bug in Python 3.4 implementation of traceback library:

>>> import traceback
>>>
>>> try:
...     1 / 0
... except Exception as e:
...     exc = e
...
>>> traceback.print_exception(exc.__class__, exc, exc.__traceback__)
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
ZeroDivisionError: division by zero
>>> 
>>> traceback.print_exception(exc.__class__, exc, None)
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
ZeroDivisionError: division by zero
>>> 
>>> traceback.print_exception(exc.__class__, exc, None, chain=False)
ZeroDivisionError: division by zero

As can be seen, giving None traceback is ignored if chain == True. This is because None is incorrectly used as a sentinel value in traceback._iter_chain (see line 135).

Note that this bug is fixed in Python 3.5 since there is a new implementation of traceback module using TracebackException objects. Will this be backported to Python 3.4? Otherwise, the bug itself should be fixed anyway.
msg324930 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2018-09-10 16:07
3.4 is out of bugfix support.
History
Date User Action Args
2022-04-11 14:58:19adminsetgithub: 68884
2018-09-10 16:07:31benjamin.petersonsetstatus: open -> closed

nosy: + benjamin.peterson
messages: + msg324930

resolution: out of date
stage: resolved
2015-07-23 14:52:20Drekincreate