cStringIO unicode weirdness

[Paul Rubin]

Josiah Carlson <josiah.carlson at sbcglobal.net> writes:
> You would be wrong.  The behavior of StringIO and cStringIO are
> different under certain circumstances, and those differences are
> intended.  Among them is when they are confronted with unicode, as you
> saw.  Another is when provided with an initializer...

The doc says there's only supposed to be a difference if the unicode
can't be represented as ascii.  That is not the case with the example
I posted.

> There is a summer of code project that is working towards making them
> behave the same, but the results will need to wait until Python 2.6
> and/or 3.0 .  Note that there are a few "closed, won't fix" bug
> reports regarding these exact same issues in the Python bug tracker at
> sourceforge.

Thanks, this helps.  At minimum the 2.5 docs should be updated to
explain the issues.