On Mon, 2007-04-09 at 13:53 -0700, Florian Apolloner wrote: > Ah now I see ;) url() is to be used if I don't need extra_directory, > any other differences?
It's purely a convenience function. Under the covers, the tuple version is converted to a call to url() in any case. The advantage of introducing url() now is that it gives us a few options for extending the URL resolving system in the future. For example, we could add more keyword arguments, if it becomes necessary for some reason. Or we -- or any third party app -- could replace the url() function with another implementation that has the same interface but works in a different fashion. Right at the moment, url() is syntactic sugar. However, it's also a nice design change to make things more extensible in the future, if we need it. Conversely, extending the tuple version without end rapidly becomes unmanageable. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
