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.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: https://github.com/Pylons/pyramid/issues/1973 on our side. ---------- messages: 252841 nosy: X-Istence priority: normal severity: normal status: open title: Changes in traceback broke existing code (Python 3.5) type: behavior versions: Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25379> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
