On Wed, 2007-03-28 at 09:45 +0400, Ivan Sagalaev wrote:
> Malcolm Tredinnick wrote:
> > Extending the URL resolving system is easier if we have an object to
> > work with instead of a tuple for those entries.
>
> Ah, I see it.
>
> However let's make it a separate issue. I'm afraid that if we start
> solving "{% url %} for generic views" issue with the "urlpatterns
> rewrite" solution we'll bury it for months.
Relax, Ivan. Changing the call from a tuple to url(...) is a ten line
change in django/conf/urls/defaults.py. It's only that long because I
had to move some code from one place to another, so the diff size
increases. Turned out that most of the work was already present in the
urlresolver.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
