Message93079
I'll take the opposite point of view:
the bad behavior was introduced with 2.5.1 (issue1548891, r52302), and
reverted for 2.5.2 because "it broke backwards compatibility with
arbitrary read buffers" (issue1730114, r53831)
The difference is in cStringIO:
>>> from cStringIO import StringIO
>>> StringIO(u"Hello, World!").read()
'H\x00\x00\x00e\x00\x00\x00l\x00\x00\x00l\x00\x00\x00o\x00\x00\x00,\x00\x00\x00
\x00\x00\x00W\x00\x00\x00o\x00\x00\x00r\x00\x00\x00l\x00\x00\x00d\x00\x00\x00!\x00\x00\x00'
The byte order is not different in the two strings: but u" " becomes
" \x00\x00\x00" and the three zeros are copied into the second item. |
|
Date |
User |
Action |
Args |
2009-09-24 16:12:17 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, fenner |
2009-09-24 16:12:17 | amaury.forgeotdarc | set | messageid: <1253808737.23.0.0938175769721.issue6988@psf.upfronthosting.co.za> |
2009-09-24 16:12:15 | amaury.forgeotdarc | link | issue6988 messages |
2009-09-24 16:12:14 | amaury.forgeotdarc | create | |
|