[issue5345] cStringIO class name typo

Changes by Benjamin Peterson : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5345] cStringIO class name typo

Alexandre Vassalotti 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. Alternatively, you could upgrade t

[issue5345] cStringIO class name typo

Virgil Dupras 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 objects are not gene

[issue5345] cStringIO class name typo

qwjqwj added the comment: This bug also exists in Python 2.6.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue5345] cStringIO class name typo

New submission from qwjqwj : It has a typo error in cStringIO.StringIO's class name "StringO": >>> import cStringIO >>> a=cStringIO.StringIO() >>> a >>> a.__class__.__name__ 'StringO' So we can't unpickle the object correctly with Python 2.5.4: >>> import pickle >>> pickle.loads(pickle.dumps(