-
Notifications
You must be signed in to change notification settings - Fork 5
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
exceptions when rendering template need better debug output #23
Comments
Here's another example of a useless stack trace:
so it's not just |
I was hit by this too:
The original backtrace (er, "traceback") is lost which is apparently the fault of the futures library. I'll try to add an option to disable the threading and hope that will make the exceptions clearer. |
I have a very crude and dirty hack for this: mvidner@7f30228. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #6 for an example
TypeError
failure with useless debug output.I'm not sure there's any way to get better debug without using a different thread handling mechanism. AFAICS the
TypeError
comes from rendering the template but I don't think it gets decorated with the number of the offending line in the template, and the stack trace resulting from #20 is in the context of the re-raise byfutures.Future
, not within the thread where it was originally raised. ICBW though - need to investigate further ...The text was updated successfully, but these errors were encountered: