Alexandre Vassalotti alexan...@peadrop.com added the comment:
This is not a typo. cStringIO.StringIO is a factory function that
returns either a cStringO object (for writing) or cStringI (for
reading). If this behavior causes a problem to you, then consider using
StringIO.StringIO.
Changes by Benjamin Peterson benja...@python.org:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5345
___
___
Virgil Dupras hs...@hardcoded.net added the comment:
The documentation says:
Another difference from the StringIO module is that calling StringIO()
with a string parameter creates a read-only object. Unlike an object
created without a string parameter, it does not have write methods. These
New submission from qwjqwj q...@papayamobile.com:
It has a typo error in cStringIO.StringIO's class name StringO:
import cStringIO
a=cStringIO.StringIO()
a
cStringIO.StringO object at 0xb7eef240
a.__class__.__name__
'StringO'
So we can't unpickle the object correctly with Python 2.5.4:
qwjqwj q...@papayamobile.com added the comment:
This bug also exists in Python 2.6.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5345
___
___
