Serhiy Storchaka added the comment: > Suggested workaround: use io.BytesIO instead of cStringIO.
Well, maybe we can replace cStringIO by io.BytesIO in cPickle (and other places). > comments on the patch... in short: your patch is changing an ABI and isn't > suitable for a maintenance release. Isn't this a private API? > I'm not sure how much we can usefully do to cStringIO in a maintenance >release. I'd be inclined to close as wontfix as io.BytesIO is available. We can't just close this issue. cStringIO crashes Python. We can use another approach. Change cStringIO so that user can't write or read more than INT_MAX bytes at a time (an exception will be raised instead of crash), but can write more than INT_MAX bytes in sum and get all string with getvalue(). This will preserve an ABI. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7358> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
