I know this isn't big (and maybe it's by design), but this didn't
happen prior to I believe -r 5516.  If you have a empty urls.py
include file in any app within the project, it causes the {% url %}
tag to not resolve for any app, even an unrelated app view.  The
exception returned is somewhere near line 205 in urlresolvers.py as
this is the trace returned.

     AttributeError at /
     'module' object has no attribute 'urlpatterns'
     Exception Type: AttributeError
     Exception Value: 'module' object has no attribute 'urlpatterns'
     Exception Location: C:\Python23\lib\site-packages\django\core
\urlresolvers.py in    _get_reverse_dict, line 205
     Python Executable: C:\Python23\python.exe
     Python Version: 2.3.5

Since the empty include doesn't have a urlpatterns, it throws the
above error... then proceeds to load the site.  I'm not sure if
something is being cached or not - but even as the site eventually
loads, none of the {% url %} template tags (that used to work prior to
the revision) resolve anymore.

The obvious work around is to just add the following to urls.py:

from django.conf.urls.defaults import *
urlpatterns = patterns('')

Just wondering if this was intended behavior or not.

Thanks,
_RK

And yeah, I know... empty urls.py files are probably bad to have
around anyway. ;)


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to