Changes between Version 3 and Version 4 of UnicodeInDjango


Ignore:
Timestamp:
01/10/2006 03:38:25 PM (9 years ago)
Author:
hugo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UnicodeInDjango

    v3 v4  
    88 * special casing: the psycopg backend will need type handlers for string types (just as it already has type handlers for date/time types)
    99 * the HTTPResponse sending machinery needs to do the unicode to DEFAULT_ENCODING translation
     10 * the HTTPRequest creation process needs to turn outside strings into unicode strings, using the provided charset (if given) or defaulting to DEFAULT_ENCODING (as that is what was sent to the browser when the form was transmitted)
     11 * special casing: what happens with GET parameters? those don't provide charsets, what should we do if DEFAULT_ENCODING is utf-8, but the GET parameters aren't valid utf-8? The clean way would be to throw an exception (like with all other places, too)
    1012 * internal usage of str() needs to be checked and supposedly changed over to unicode() usage
    1113 * debugging stuff needs to use repr() on strings, not str() (or use unicode() and let the HTTP response handling stuff handle the conversion - most debugging stuff is working with the response machinery anyway)
Back to Top