#5875: Non-ascii chars in source code causing UnicodeEncodeError for default 500
error handler, resulting in non-descriptive traceback-only error page
----------------------------+-----------------------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  nobody        
     Status:  reopened      |            Component:  Core framework
    Version:  SVN           |           Resolution:                
   Keywords:                |                Stage:  Accepted      
  Has_patch:  0             |           Needs_docs:  0             
Needs_tests:  0             |   Needs_better_patch:  0             
----------------------------+-----------------------------------------------
Comment (by [EMAIL PROTECTED]):

 I am sorry, but I seem to be unable to generate a good testcase against
 current SVN.

 The code which triggered the report is being ported from 0.96 to current
 SVN, and did some interesting things with non-ascii chars, but I am not
 able to replicate that in small testcase.

 You can probably close this bug at this time, as this might be more a
 problem in our code then in Django.
 If I can figure this out with a good testcase, should I reopen this bug,
 or start a new one ?

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