This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients benjamin.peterson, hynek, pitrou, serhiy.storchaka, stutzbach
Date 2014-02-02.22:31:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391380309.45.0.334751128789.issue20435@psf.upfronthosting.co.za>
In-reply-to
Content
But how then other values of newline except '\n' can be useful?

The problem is that newline converting is applied twice, in write() and in read(). When constructor uses write() and getvalue() returns same value as read(), we have no chance to get newlines encoded or decoded only once. Current results for newline != '\n' looks meanless to me.

Here is my half-baked patch. It fixes only _pyio.StringIO, but _io.StringIO are still partially broken. The patch also contains new tests.
History
Date User Action Args
2014-02-02 22:31:49serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, benjamin.peterson, stutzbach, hynek
2014-02-02 22:31:49serhiy.storchakasetmessageid: <1391380309.45.0.334751128789.issue20435@psf.upfronthosting.co.za>
2014-02-02 22:31:49serhiy.storchakalinkissue20435 messages
2014-02-02 22:31:49serhiy.storchakacreate