You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changes in traceback broke existing code (Python 3.5) #69566
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:
Activity
bertjwregeer commentedon Oct 12, 2015
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.py 1108 includeme2 config.add_view(view2)
pyramid/util.py 526 wrapper return wrapped(self, *arg, **defaults)
pyramid/util.py 557 wrapper f = traceback.extract_stack(limit=4)
/Users/xistence/.pyenv/versions/3.5.0/lib/python3.5/traceback.py 201 extract_stack stack = StackSummary.extract(walk_stack(f), limit=limit)
What it used to look like on Python 3.4:
pyramid/config/init.py 798 include c(configurator)
pyramid/tests/test_config/test_init.py 1108 includeme2 config.add_view(view2)
pyramid/util.py 526 wrapper return wrapped(self, *arg, **defaults)
pyramid/util.py 557 wrapper f = traceback.extract_stack(limit=4)
Notice that in the Python 3.5 version:
/Users/xistence/.pyenv/versions/3.5.0/lib/python3.5/traceback.py 201 extract_stack stack = StackSummary.extract(walk_stack(f), limit=limit)
Is added.
We are tracking this issue here: Pylons/pyramid#1973 on our side.
bertjwregeer commentedon Oct 12, 2015
Looks like this is a dup of: https://bugs.python.org/issue25108
berkerpeksag commentedon Oct 12, 2015
Thanks for the report! Yes, this is a duplicate of bpo-25108. It would be great if you have time to test it with the current 3.5 branch.