On Apr 21, 1:53 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> [snip]
> We haven't documentedreverse() anywhere, as far as I know. So worth
> filing a ticket.
>
I realize that urlresolvers.reverse() was not documented earlier, but
does the addition of named urls mean that the old behavior is still
going to be broken or will it be preserved for unambiguous matches?
I had been using
urlresolvers.reverse('viewname', kwargs={ 'captured_arg': myarg})
to avoid putting hardcoded urls in my view's Http redirects.
-Chris
BTW: many thanks for all the django teams great work!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
