Break what apparently is a cycle involving custom User model and QuerySet.as_manager()
#2377
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.
Break a cycle resulting in
[django-manager-missing]
I'm not sure if my treatment is correct, perhaps I'm just treating symptoms of some deeper problem. However, this at least makes a test case extracted from my real system pass, and removes a dozen of
django-manager-missing
errors in my code (actually all of them!).See the contributed test case for details - I don't really see how to summarize it any better.
There seems to be some cycle during semanal, where
base_as_manager.type
remainsNone
during all iterations (yes, I tried deferring first). This seems to only affect the baseQuerySet
and require customAUTH_USER_MODEL
.Prior to the fix, the test failed with the following: