[issue11716] mixing calls to io.TextIOWrapper.write and io.BufferedWriter.write produces undefined results

Sean Sherrard added the comment: Never mind, I didn't realize that TextIOWrapper was doing its own buffering. The behaviour makes sense to me now after reading textio.c -- resolution: -> invalid status: open -> closed ___ Python tra

[issue11716] mixing calls to io.TextIOWrapper.write and io.BufferedWriter.write produces undefined results

New submission from Sean Sherrard : Maybe this is by design, but it certainly took me by surprise. Steps to reproduce: Python 3.2 (r32:88445, Feb 20 2011, 21:29:02) [MSC v.1500 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more info