On Mon, 2008-09-15 at 01:04 -0700, catsclaw wrote:
> Hi all --
>
> Is the url dispatcher completely fubared? I cannot get it to work
> at all. I'll have working {% url %} tags, add a single print
> statement to a source file, and then have the reverse lookup throw a
> TemplateSyntaxError, without my touching the urls.py file or the
> template file.
> I'm also seeing that named entries in the urlresolvers will fail
> if they're in a secondary file and brought into the site urls using
> the include() function. They work perfectly if they're copied and
> pasted directly into the main urls.py.
> These are in addition to the problem I reported last week (where
> the order of entries in urls.py determined whether a given lookup
> succeeded). In short, as far as I can tell the reverse() urlresolver
> system is just broken. Are people just not using it? Are there
> substitutes, or should we just hard-code the URLs?
It's not broken and people are using it. There's also a complete test
suite for it in tests/regressiontests/urlpatterns_reverse/ that passes.
You're going to have to reign in the emotion a bit and resort to posting
some actual details of the problems you're seeing. A short example that
reliably demonstrates the problem so that other people can repeat it and
either work out what you're doing wrong or if there's a bug in the code.
It's not impossible that there are bugs (in fact there are bugs; I know
of at least two that have been reported in Trac that look legitimate),
but the whole concept isn't fatally flawed or anything.
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
-~----------~----~----~----~------~----~------~--~---
