| commit | a883a3d5fdfefdf198bd34f6d07273063bc1f3b5 | [log] [tgz] |
|---|---|---|
| author | Guido van Rossum <guido@python.org> | Mon Apr 29 13:54:48 2002 +0000 |
| committer | Guido van Rossum <guido@python.org> | Mon Apr 29 13:54:48 2002 +0000 |
| tree | db37a916190c759d44f2f318779961f953a9acf7 | |
| parent | 81b9251d5996ec89bcc016c29ecc0b5f0204e59b [diff] |
See discussion at SF bug 547537. Unicode objects are currently taken as binary data by the write() method. This is not what Unicode users expect, nor what the StringIO.py code does. Until somebody adds a way to specify binary or text mode for cStringIO objects, change the format string to use "t#" instead of "s#", so that it will request the "text buffer" version. This will try the default encoding for Unicode objects. This is *not* a 2.2 bugfix (since it *is* a semantic change).