Good question. The issue of encoding is a little murky. As of now, my
(almost working) patch will pretty much try to encode everything
(using force_to_unicode) *except* data in a file upload.
I'm not exactly sure we'll ever support encoding data in file uploads,
but if we do it's definitely a tricky problem.
The issue is two-fold:
- What files should we encode and which shouldn't we? (do we do
matching on the mimetype? that doesn't sound nice)
- Dealing with multibyte boundaries in the strings while streaming
the data. (Not a question, just a fun night of work.)
Anyway, I'll go back to ignoring that issue for now unless I get angry
cries for it.
-Mike
On Mar 19, 7:06 am, "Casper Jensen" <
t...@...> wrote:
> The filename returned by UploadedFile, will that be an unicode object
> or a string? Currently request.FILES uses string objects for the
> filenames, which results in some problems with uploaded files with
> non-latin filenames. See #6009.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to
django-developers@...
To unsubscribe from this group, send email to
django-developers-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en-~----------~----~----~----~------~----~------~--~---
