On Feb 14, 12:04 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> That's because you are expecting things from reverse() that it
> explicitly doesn't do. In particular, the "args" and "kwargs" parameters
> to reverse are only checked against capturing groups in the URL's
> regular expression.
>
> The reason for this is that to also permit people to specify things in
> extra_dict will rapidly (in fact, already has when people suggested
> this) lead to confusion about what is and isn't possible and how Python
> actually works. String matching is easy: all strings with the same value
> compare as equal. But then people start wanting to put QuerySets in
> there or other class instances or complex objects that have interesting
> equality comparison behaviour and the slippery slope leads straight to
> hell. So, to maintain sanity all around, you can't do that, as you've
> discovered. That's intentional.
LOL, my sanity has been questionable for years.
> Fortunately, there's a solution, I'm pretty sure:
>
> (r'^(?P<myname>drink)/', include(app.urls))
> (r'^(?P<myname>eat)/', include(app.urls))
>
> or, even more succintly:
>
> r'^(?P<myname>eat|drink)/', include(app.urls))
>
> These might trip across other urlresolver bugs, from memory (I have a
> feeling the bug still exists where if we don't match the first item
> that's a potential candidate, we fail unconditionally, rather than
> testing everything). In any case, I'll check out those side cases in the
> next few hours, since I'm doing some trunk work at the moment and this
> has come up.
>
> So either the alternatives work right now or will work within a day or
> two. That's certainly the way to approach this, though, because the
> other way just opens up the door to far too many user problems.
Your memory is quite good. I did try exactly what you suggested many
hours ago today and saw the result you describe (see below). If the
first item does not match it fails. So I figured I still didn't have
the syntax correct or something.
Presumably the url template tag will perform similarly to reverse when
the fix is made? So this would be equivalent:
{% url 'food-view' myname='drink' %}
Thanks so much for your help Malcolm.
urlpatterns = patterns('',
(r'^(?P<myname>drink)/', include('app.urls')),
(r'^(?P<myname>eat)/', include('app.urls')),
)
>>> reverse('food-view', kwargs={'myname':'drink'})
'/drink/'
>>> reverse('food-view', kwargs={'myname':'eat'})
Traceback (most recent call last):
File "<console>", line 1, in ?
File "c:\django\trunk\django\core\urlresolvers.py", line 297, in
reverse
return iri_to_uri(u'/' + get_resolver(urlconf).reverse(viewname,
*args, **kw
args))
File "c:\django\trunk\django\core\urlresolvers.py", line 283, in
reverse
return u''.join([reverse_helper(part.regex, *args, **kwargs) for
part in sel
f.reverse_dict[lookup_view]])
File "c:\django\trunk\django\core\urlresolvers.py", line 88, in
reverse_helper
result = re.sub(r'\(([^)]+)\)', MatchChecker(args, kwargs),
regex.pattern)
File "C:\Python24\lib\sre.py", line 142, in sub
return _compile(pattern, 0).sub(repl, string, count)
File "c:\django\trunk\django\core\urlresolvers.py", line 129, in
__call__
raise NoReverseMatch("Value %r didn't match regular expression %r"
% (value,
test_regex))
NoReverseMatch: Value 'eat' didn't match regular expression 'drink'
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
