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 draghuram
Recipients amaury.forgeotdarc, christian.heimes, draghuram, gvanrossum
Date 2007-11-07.17:08:55
SpamBayes Score 0.0023931626
Marked as misclassified No
Message-id <1194455337.8.0.268769343343.issue1395@psf.upfronthosting.co.za>
In-reply-to
Content
I am attaching another  patch (io2.diff). Please review. I am not sure
whether _adjust_chunk() should also adjust "readahead".

BTW, PEP 3116 says:

"If universal newlines without translation are requested on input (i.e.
newline=''), if a system read operation returns a buffer ending in '\r',
another system read operation is done to determine whether it is
followed by '\n' or not. In universal newlines mode with translation,
the second system read operation may be postponed until the next read
request, and if the following system read operation returns a buffer
starting with '\n', that character is simply discarded."

I suppose this issue is mainly talking about the latter (newline is
None). I don't understand what is meant by "enabling universal new line
mode without translation". Isn't the purpose of enabling universal new
line mode is to translate line endings? I may be missing something
basic, of course.
Files
File name Uploaded
io2.diff draghuram, 2007-11-07.17:08:56
History
Date User Action Args
2007-11-07 17:08:58draghuramsetspambayes_score: 0.00239316 -> 0.0023931626
recipients: + draghuram, gvanrossum, amaury.forgeotdarc, christian.heimes
2007-11-07 17:08:57draghuramsetspambayes_score: 0.00239316 -> 0.00239316
messageid: <1194455337.8.0.268769343343.issue1395@psf.upfronthosting.co.za>
2007-11-07 17:08:57draghuramlinkissue1395 messages
2007-11-07 17:08:56draghuramcreate