Skip to content

Commit c9b1a0f

Browse files
More port planning.
1 parent 2fcade6 commit c9b1a0f

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

2to3-done.txt

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -208,3 +208,18 @@ Joseph S. Myers notes:
208208
>you describe as systems programs in your porting HOWTO. I don't think
209209
>Roundup really is such a systems program, except in limited areas such as
210210
>dealing with attached files.
211+
212+
>For network data, Roundup is already careful about character sets -
213+
>converting to UTF-8 on input (see e.g. "if client charset is different
214+
>from the storage charset, recode form fields" in cgi/client.py, or the
215+
>code in mailgw.py that checks the encoding of each MIME part and converts
216+
>to UTF-8). Presumably in such cases the decoding would remain unchanged
217+
>for Python 3, but the encoding should be a function that's a no-op for
218+
>Python 3 to get native str objects there (and likewise for the places
219+
>where data is turned into Python 2 unicode objects, processed and
220+
>converted back to UTF-8 - both steps should be no-ops for Python 3).
221+
>
222+
>For reading templates, database string data, etc., Roundup knows the
223+
>storage format is UTF-8 so has no explicit conversions - those are places
224+
>that will need to be found and made to decode as UTF-8 for Python 3 (or do
225+
>a no-op for Python 2).

0 commit comments

Comments
 (0)