On Mon, 2008-09-08 at 20:34 -0700, catsclaw wrote:
> Hey all --
>
> I just can't get the urlresolvers.reverse() to work, and I think I
> found a bug in it. I have a "logout" method defined in two files, a
> users.py file and a home.py file. There's also two views mapped in
> the urls.py file, a "myapp.users.logout" and a "myapp.home.logout".
>
> In my code, if I have the following lines:
>
> print urlresolvers.reverse('myapp.home.logout')
> print urlresolvers.reverse('myapp.users.logout')
>
> ... I get two urls printed to output. If, instead, I have ...
>
> print urlresolvers.reverse('myapp.users.logout')
> print urlresolvers.reverse('myapp.home.logout')
>
> ... the first call fails with the following error:
>
> NoReverseMatch at /myapp/svn/
> Reverse for '<function logout at 0x030594F0>' with arguments '()' and
> keyword arguments '{}' not found.
>
> Any suggestions what's going on, here? Is this a bug, or am I missing
> something obvious?
Can you please show the URLConf lines that are involved. If the final
files are included from some higher up urls.py files, please include the
lines that do the including.
There might be a bug here. The fact that changing the order changes the
behaviour is certainly suspicious. But it's not possible to work out
what's really going on without knowing the patterns involved (the bug
could be that the first version works when it shouldn't).
Also do things change (e.g. work consistently) if you use the
url(patterns, view, name="foo") version of the pattern and do a reverse
lookup for the two different "names"?
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
-~----------~----~----~----~------~----~------~--~---
