Do many related manager creation during semantic analysis #2231
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.
When finding a
ManyToManyField
we can directly create 2ManyRelatedManager
s, one for each side of the relation. This makes the model declaring theManyToManyField
be the one who contributes theManyRelatedManager
s.Trying to place some related code closer to each other. This time we move some code out of the type checking phase to semantic analysis.
Refs:
ManyToManyDescriptor
and fixModel.<manytomany>.through
typing #1805ManyRelatedManager.through
attribute and generic type parameter #2026