Skip to content
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

Include traceback when wrapping import errors #450

Closed
wants to merge 1 commit into from
Closed

Include traceback when wrapping import errors #450

wants to merge 1 commit into from

Conversation

@wolever
Copy link

@wolever wolever commented Oct 11, 2011

Without the complete tracebacks it's fairly frustrating to try and track down the import errors.

@wolever
Copy link
Author

@wolever wolever commented Oct 11, 2011

Note: I haven't yet tested the multiprocessing and jinja2 handlers. They look like they should work, though, and if this patch is going to be accepted I'll test them properly.

@wolever wolever closed this Oct 11, 2011
@wolever wolever reopened this Oct 11, 2011
@bitprophet
Copy link
Member

@bitprophet bitprophet commented Oct 11, 2011

I actually think I do display the traceback for the multiprocessing import, for this very reason, but it looks like that was not considered for those other optional requirements. Good catch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants