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 aesthetics. Many people complained to me that Django has the "ugly ORM syntax with underscores". > You still need to parse kwargs to handle queries across joins (e.g., > Article.objects.filter(author__name__exact='fred')) ...which can be replaced with tuples easily thus eliminating parsing. ;-) Thanks, Eugene --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
