[issue25379] Changes in traceback broke existing code (Python 3.5)

Berker Peksag added the comment: Thanks for the report! Yes, this is a duplicate of issue 25108. It would be great if you have time to test it with the current 3.5 branch. -- components: +Library (Lib) nosy: +berker.peksag resolution: -> duplicate stage: -> resolved status: open -> cl

[issue25379] Changes in traceback broke existing code (Python 3.5)

Bert JW Regeer added the comment: Looks like this is a dup of: https://bugs.python.org/issue25108 -- ___ Python tracker ___ ___ Python

[issue25379] Changes in traceback broke existing code (Python 3.5)

New submission from Bert JW Regeer: One of the changes in Python 3.5's traceback functionality broke existing code compared to Python 3.4 by injecting an extra stack frame into the list when using traceback.extract_stack: What this looks like on Python 3.5: pyramid/tests/test_config/test_init