#30303: Error handler page generating unicode decode error.
---------------------------------+--------------------------------------
Reporter: Kevin Golding | Owner: (none)
Type: Bug | Status: closed
Component: Error reporting | Version: 2.2
Severity: Normal | Resolution: needsinfo
Keywords: wsgi unicode | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
This doesn't reproduce as far as we can see. I'm going to close this as
`needsinfo`.
As I said, the error is coming up when loading the 500 error template:
{{{
with Path(CURRENT_DIR, 'templates', 'technical_500.html').open()
as fh:
t = DEBUG_ENGINE.from_string(fh.read())
}}}
Here the question is why is the `ascii` encoding being used? From
[https://docs.python.org/3.7/library/functions.html#open the `open()`
docs]:
> The default encoding is platform dependent (whatever
`locale.getpreferredencoding()` returns)...
This looks like an environment issue.
**Very happy** to re-look you can provide a sample project demonstrating
the issue that shows Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/30303#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.2eaa9796278caae5d888291249c0f118%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
