#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]):
Well, I talk about it in the description, "this badly", "mod_apache error
handler" and so on, but I could be clearer in the description, sure.
Anway, yes, django choking on its own error handler is the concrete
problem.
Will serving as UTF-8 resolve problems with non-unicode strings used in
source ?
From my point of view, handling this error scenario "softer" than now is
the priority.
Django should of course clearly indicate when there are encoding issues,
and not do best-effort and get it wrong, but better error handling would
be nice to have.
--
Ticket URL: <http://code.djangoproject.com/ticket/5875#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
