Changes between Version 10 and Version 11 of TracDev/UnicodeGuidelines

Timestamp:

Sep 26, 2008, 3:42:07 PM (16 years ago)

Author:

Christian Boos

Comment:

Add some additional information about unicode at system boundaries

TracDev/UnicodeGuidelines

@@ -225 +225 @@
 [source:/trunk/trac/db/sqlite_backend.py@head#L58 SQLiteUnicodeCursor], for pysqlite1.
 
+=== The console ===
+
+When reading from the console, we assume the text is encoded
+using `sys.stdin.encoding`.
+
+When writing to the console, we assume that the `sys.stdout.encoding`
+should be used.
+
+The logging API seems to handle `unicode` objects just fine.
+
 === Filesystem objects ===
 
@@ -236 +246 @@
 using non-ascii characters. In Python, it should be safe to provide `unicode`
 objects for all the `os` filesystem related functions.
+
+Look also at r7360, r7361, r7362.
+
+More information about how Python deals with Python at system boundaries can be found here: http://kofoto.rosdahl.net/wiki/UnicodeInPython.
+
+
 
 === `versioncontrol` subsystem ===
@@ -282 +298 @@
 If this is the case, that encoding is used.
 
-=== The console ===
-
-When reading from the console, we assume the text is encoded
-using `sys.stdin.encoding`.
-
-When writing to the console, we assume that the `sys.stdout.encoding`
-should be used.
-
-The logging API seems to handle `unicode` objects just fine.
-
 === Interaction with plugins ===