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 catlee
Recipients catlee
Date 2013-06-08.00:52:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370652753.2.0.115220958335.issue18167@psf.upfronthosting.co.za>
In-reply-to
Content
This is a possible fix to this issue. It's not as clean as I'd like, but the simpler versions I tried could end up with the entire file contents in memory for degenerate (or malicious) inputs.

The trick is handling the case where the current line ends with \r. We can't know if this is just a normal character in the file, or represents the end of a line until we see the start of the next line.
History
Date User Action Args
2013-06-08 00:52:33catleesetrecipients: + catlee
2013-06-08 00:52:33catleesetmessageid: <1370652753.2.0.115220958335.issue18167@psf.upfronthosting.co.za>
2013-06-08 00:52:33catleelinkissue18167 messages
2013-06-08 00:52:32catleecreate