Changes between Version 10 and Version 11 of TracDev/UnicodeGuidelines
- Timestamp:
- Sep 26, 2008, 3:42:07 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/UnicodeGuidelines
v10 v11 225 225 [source:/trunk/trac/db/sqlite_backend.py@head#L58 SQLiteUnicodeCursor], for pysqlite1. 226 226 227 === The console === 228 229 When reading from the console, we assume the text is encoded 230 using `sys.stdin.encoding`. 231 232 When writing to the console, we assume that the `sys.stdout.encoding` 233 should be used. 234 235 The logging API seems to handle `unicode` objects just fine. 236 227 237 === Filesystem objects === 228 238 … … 236 246 using non-ascii characters. In Python, it should be safe to provide `unicode` 237 247 objects for all the `os` filesystem related functions. 248 249 Look also at r7360, r7361, r7362. 250 251 More information about how Python deals with Python at system boundaries can be found here: http://kofoto.rosdahl.net/wiki/UnicodeInPython. 252 253 238 254 239 255 === `versioncontrol` subsystem === … … 282 298 If this is the case, that encoding is used. 283 299 284 === The console ===285 286 When reading from the console, we assume the text is encoded287 using `sys.stdin.encoding`.288 289 When writing to the console, we assume that the `sys.stdout.encoding`290 should be used.291 292 The logging API seems to handle `unicode` objects just fine.293 294 300 === Interaction with plugins === 295 301