#8726: Unicode-errors with url-tags after changeset 8760
------------------------------------+---------------------------------------
          Reporter:  Uninen         |         Owner:  mtredinnick       
            Status:  new            |     Milestone:  1.0               
         Component:  Uncategorized  |       Version:  SVN               
        Resolution:                 |      Keywords:  url, urls, unicode
             Stage:  Unreviewed     |     Has_patch:  0                 
        Needs_docs:  0              |   Needs_tests:  0                 
Needs_better_patch:  0              |  
------------------------------------+---------------------------------------
Comment (by mtredinnick):

 We're going need to some more information to be able to repeat this,
 because the description doesn't have the critical piece. You can see in
 [8766] that there are now tests which do exactly what is described (there
 were previously tests that were very similar and using non-ASCII
 characters, but I added a couple that were even closer to this ticket) and
 they don't fail.

 So if you could come up with a variation on those tests that does fail,
 that would be great. Failing that, a small example of what you are passing
 to the URL tag and what you URLConf looks like. If the critical URLConf is
 included inside another one, we need them all the way back to the top in
 case it is a variant on #8725.

 If the problem's been fixed after [8763], also, please close this ticket.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8726#comment:8>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to