On Wed, 2008-02-13 at 15:22 -0800, grahamu wrote:
[...]
> >>> reverse('eat')
> Traceback (most recent call last):
[...]
> NoReverseMatch
>
> Is there a workaround for this issue? Am I doing something
> incorrectly?
As Alex pointed out, you're calling reverse() on something that isn't a
direct URL pattern. Don't do that. It makes no sense to call reverse()
on something that is actually a collection of URL patterns. Instead,
pick one of the URL patterns inside urls2 and call reverse on that.
> Should I file a ticket?
The only semi-bug here is maybe that we don't issue a warning if you
pass a name to something with an include(). We do correctly raise an
error if you try to use the name in reverse(), though (The case where
you called reverse('drink') worked correctly, since it was for a
specific, unambiguous URL pattern). There's no bug there.
You might like to open a ticket for the warning issue. However the type
of call you're trying to make is not intended to work; it just doesn't
make sense in the general case.
Regards,
Malcolm
--
I just got lost in thought. It was unfamiliar territory.
http://www.pointy-stick.com/blog/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
