[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-13 Thread Andrew Svetlov
Andrew Svetlov added the comment: Patch applied -- nosy: +asvetlov resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-13 Thread Roundup Robot
Roundup Robot added the comment: New changeset ba055ccd99ef by Andrew Svetlov in branch 'default': Issue #15571: comment the fact what python impl of TextIOWrapper always works in write_throuth mode http://hg.python.org/cpython/rev/ba055ccd99ef -- nosy: +python-dev

[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-07 Thread Chris Jerdonek
Chris Jerdonek added the comment: Attaching patch. -- keywords: +patch Added file: http://bugs.python.org/file26716/issue-15571-1.patch ___ Python tracker ___ ___

[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-07 Thread Nick Coghlan
Nick Coghlan added the comment: Ah, thanks. Yes, that could definitely use a comment :) -- priority: release blocker -> normal stage: test needed -> needs patch type: behavior -> enhancement ___ Python tracker

[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-07 Thread Chris Jerdonek
Chris Jerdonek added the comment: The fact that the Python implementation doesn't look at write_through doesn't necessarily mean that it's not respected. It could always write through. Indeed, it looks like this is the case and was discussed at one point: http://bugs.python.org/issue12591#ms

[issue15571] Python version of TextIOWrapper ignores "write_through" arg

2012-08-06 Thread Nick Coghlan
New submission from Nick Coghlan: In discussing #15216, I noticed that the write_through parameter is completely unused in the Python implementation of TextIOWrapper. That also means we have a hole in the test coverage: there is no test that is run on both the C and Python versions to ensure t