#19357: Unicode errors when Django is installed under a non-ASCII path
---------------------------------+-------------------------------------
Reporter: kujiu | Owner: aaugustin
Type: Bug | Status: new
Component: Python 2 | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by kmtracey):
Wait, what? It ought to be OK to pass unicode on Python 2.X to Python os
path functions. Yes, internally Python is going to have to turn unicode
into a bytestring for passing into the system functions...but it should be
able to do that, we should not have to do it before calling the os path
functions. We've gone back and forth on this before, see for example
#11030. Django code CANNOT be responsible for figuring out what the right
encoding is for file system paths -- utf8 is going to be wrong on Asian
windows systems, for example. Underlying Python should be configured
correctly to figure that out. Or am I misunderstanding what you are having
to do here....?
--
Ticket URL: <https://code.djangoproject.com/ticket/19357#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
