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.

Author X-Istence
Recipients X-Istence
Date 2015-10-12.04:42:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444624940.12.0.845916385151.issue25379@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2015-10-12 04:42:20X-Istencesetrecipients: + X-Istence
2015-10-12 04:42:20X-Istencesetmessageid: <1444624940.12.0.845916385151.issue25379@psf.upfronthosting.co.za>
2015-10-12 04:42:20X-Istencelinkissue25379 messages
2015-10-12 04:42:19X-Istencecreate