Russell Keith-Magee wrote:
> You still need to parse kwargs to handle queries across joins (e.g.,
> Article.objects.filter(author__name__exact='fred'))
Just playing around with ideas, but what if you could do something like:
Article.objects.filter(author=Author.objects.filter(name='fred'))
It's
Eugene Lazutkin wrote:
> What was the motivation behind using complex kwargs like (taken from
> http://code.djangoproject.com/wiki/RemovingTheMagic):
The complex kwargs predate magic-removal. Most of the magic kwargs are
slowly disappearing, too, like the sudden recent introduction of
.exclud
Last night in #django a couple of good points were brought up by
someone who was just starting to explore Django and had decided to
learn from magic-removal rather than trunk; both of them, I think, are
worthy of discussion, so here goes:
1. The new example of usage for a generic view is counteri
Russell Keith-Magee wrote:
>
> Interesting, but I'm not sure I see the advantage. I don't think this
> notation is inherently more obvious, and I don't see any use cases
> that the existing notation does not service, but this notation would
> be able to service.
I don't see either. It is a pure
