#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 mtredinnick):
By the way, we'll still need an example of how to reproduce this problem.
There's already quite a lot of tolerance for displaying invalid characters
in the technical_500_handler() function, so if you're able to cause the
crash with valid code in current subversion trunk, please post a short
example of how to do this.
I'm not inclined to move to any kind of softer error handling in terms of
using "replace" or "ignore" anywhere there. We should never be sending out
bad data and, if we are, it must be caught somewhere. We are permissive in
what we accept (form input, etc) and strict in what we produce. Best
practice.
--
Ticket URL: <http://code.djangoproject.com/ticket/5875#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
