Show the search paths in case of an import error #39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Sorry @PhilipGarnero I merged your other pull request before this one. Now this one doesn't work any more. Do you mind rebasing that onto master? Thanks. |
PhilipGarnero
force-pushed
the
search_paths
branch
from
ee79823 to
1c12d8c
Compare
Contributor
Author
|
I was expecting it ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The import errors were hard to debug due to the lack of information about directories being searched.
I filled the search_path in order for it to be displayed when an import error occurs.
To test, uncomment the test
test_no_extension(it is failing because of an import), run the tests and check the error message.