#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: closed | Component: Core framework
Version: SVN | Resolution: wontfix
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------+-----------------------------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
This is not the right fix. We ''should'' be raising errors when bad data
is passed in, not quietly disguising it. If your code is generating
invalid data, it should be caught. If you want to replace whatever code it
is you're changing in your local copy (since the patch doesn't identify
the path to the file, I can only guess you're patching
{{{django.http.__init__.py}}}, go for it, but this isn't a patch for core.
It's not clear from your description what the root cause of the problem
is. Try to construct a small example demonstrating it and post to django-
users to get some help if you need to. Remember that you ''must'' use
UTF-8 encoded bytestrings in any data you pass to Django, if they're not
unicode objects.
--
Ticket URL: <http://code.djangoproject.com/ticket/5875#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
