#9315: Keyword arguments with spaces and the url tag
--------------------------------------+-------------------------------------
          Reporter:  alexisbellido    |         Owner:  nessita                 
    
            Status:  assigned         |     Milestone:  1.1                     
    
         Component:  Template system  |       Version:  1.0                     
    
        Resolution:                   |      Keywords:  url, tplrf-fixed, 
pycamp2009
             Stage:  Accepted         |     Has_patch:  1                       
    
        Needs_docs:  0                |   Needs_tests:  0                       
    
Needs_better_patch:  0                |  
--------------------------------------+-------------------------------------
Comment (by mtredinnick):

 I'm not going to apply the changes to the `split_contents()` portion,
 since they don't appear to fix an existing problem I'm not convinced they
 don't introduce a bug. We should fix on problem per ticket.

 If somebody wants to fix up that portion (and if it can be reduced to one
 line, that would be great), the patch should include test of the i18n
 pieces in that function. It's clearly looking at `_("...")` strings, but I
 don't see anything in the replacement code that handles that. It might
 well be being handled elsewhere automatically (so we're doing it twice
 now) and that will be demonstrated by the tests in the new ticket and
 patch.

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