-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Uninformative stack traces on import errors #67
Comments
Thanks Ben!! |
Glad I could help @canyon289! Did my suggestion of running I can open a PR for this shortly. This is a quick one, but it was too late for me last night. |
I didnt get a chance, I'll try it out tomorrow |
Proposed fix is up in #72. @canyon289 I'm still interested in knowing what went wrong with your environment, so please do send me the stack trace when you get the chance. |
Thanks @canyon289! This should now be handled better by #72. |
I think it'd help to put the import statements inside of
def compile_X_model
, because otherwise information about theImportError
isn't being passed on.The text was updated successfully, but these errors were encountered: