#11559: urlresolvers.reverse do not work with namespaced urls and captured
parameters in parent urlconf
----------------------------------------+-----------------------------------
          Reporter:  kmik...@gmail.com  |         Owner:  nobody
            Status:  new                |     Milestone:        
         Component:  Core framework     |       Version:  SVN   
        Resolution:                     |      Keywords:        
             Stage:  Someday/Maybe      |     Has_patch:  0     
        Needs_docs:  0                  |   Needs_tests:  0     
Needs_better_patch:  1                  |  
----------------------------------------+-----------------------------------
Changes (by cwb):

 * cc: calle...@gmail.com (added)
  * needs_better_patch:  0 => 1

Comment:

 In case anyone is interested in a hack -- not a proper solution -- I've
 attached a patch (against 1.1). Playing around in urlresolvers.py left me
 almost as clueless as before about its mechanics, so I'm convinced I'm
 missing edge (or non-edge!) cases. I needed this to multiply up a number
 of app URLs with various (parameterised) prefixes, giving them different
 and predictable names for reversing, but found later namespaces didn't
 support that (either) -- something to do with only one urlconf being
 searched per namespace unless I misunderstood something. Thus, I abandoned
 them and wrote a custom url include function instead. That means this hack
 has hardly seen any use.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11559#comment:7>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to