#7768: r 'str' object is not callable in base.py
------------------------------------------------------------------------+---
Reporter: William Martinez Pomares <wmarti...@avantica.net> |
Owner: nobody
Status: closed |
Milestone:
Component: Core framework |
Version: SVN
Resolution: duplicate |
Keywords:
Stage: Unreviewed |
Has_patch: 0
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------------------------+---
Changes (by kmtracey):
* status: reopened => closed
* resolution: => duplicate
Comment:
While your exact reproduction scenario may differ from what is detailed in
#6442, it sounds to me like the fix proposed for #6442 would cover this
case as well. The fix suggested there is:
"I suggest that urlresolver would raise an exception on invalid look-ups."
If that fix were in place, then the resolve() call would raise an error
instead of returning a string, and you'd never get to the point where
subsequent code tried to call a string object.
So I'd say your scenario is just a different way of tripping over the same
bug -- you just have a different way of injecting an invalid lookup into
your urls.py. If you'd like to ensure your case is considered when #6442
is fixed, the right place to mention it is in #6442 itself, not here. We
only need one open ticket to track improving this error situation.
--
Ticket URL: <http://code.djangoproject.com/ticket/7768#comment:12>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
