Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
IndexError when showing traceback at Pylons #135
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.
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.
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.