Fix potential circular import edge-case #201
Merged
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
|
Just a note that I've spent 6 hours today trying to replicate the issue with tests in django-rest-framework-json-api without any success. The problem is visible specifically during testing in our rather complex app, which makes it really hard to reproduce. It seems to relate to when files are first imported, as it specifically fails during test collection in our suite. At any rate, I'm not the only one having experience this ref #158, and the fix is simple enough and did indeed solve my case. |
jsenecal
added a commit
that referenced
this pull request
Feb 6, 2016
Fix potential circular import edge-case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes #158