Simon Willison wrote: > I don't see any harm in META using unicode strings, whereas > if it were to use bytestrings our documentation ends up being that > little bit more confusing (we can't just claim everything is a > unicode string).
We can't do it anyway. First example is "raw_post_data" that should be in bytes and on the other and are files passed to HttpResponse. > If there are any practical disadvantages to META containing unicode > strings I confess I can't invent any real disadvantages from the top of my head. Unless may be the inconsistency between raw form data submitted via GET being in unicode while submitted via POST - in byte string. --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
