-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexError when showing traceback at Pylons #135
Comments
Anonymous wrote: I don't think it is a duplicate because the exception in this case is IndexError not AttributeError. I can't manage to get a standalone test case, but as long as there is a way to raise a mako exception with an empty traceback (i.e. None), a mako IndexError will be generated. |
Anonymous wrote: This bug is related to [http://pylonshq.com/project/pylonshq/ticket/612 Pylons ticket #612]. It seems that each part blames the other, resulting in a developer deadlock. I think Mako should catch IndexError and Pylons should not call the Mako html_error_template() with an empty traceback. |
Changes by Michael Bayer (@zzzeek):
|
Migrated issue, originally created by Anonymous
Pylons has a _debug controller that shows past exception tracebacks. When a user follows the debug link shown in console an exception occurs:
In particular, trcback is None so any index value would raise an IndexError. This would also be Pylon's fault as the exception is not properly replayed.
A patch is attached.
Attachments: pylons_fix
The text was updated successfully, but these errors were encountered: