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 gregory.p.smith
Recipients amicitas, giampaolo.rodola, gregory.p.smith, neologix, rosslagerwall
Date 2011-03-16.06:03:39
SpamBayes Score 0.00023443693
Marked as misclassified No
Message-id <1300255420.66.0.417319235522.issue11459@psf.upfronthosting.co.za>
In-reply-to
Content
ross's patch looks good to me.

Isn't the behavior just plain broken in 3.1 and 3.2?  The docs say that the default bufsize=0 is unbuffered in Popen but the implementation has that nasty XXX to make it line buffered instead of unbuffered in it.

This appears to have hid the problems with the textiowrapper being used in os.popen.

I think fixing it in 3.1 and 3.2 is the right thing to do.

It is desirable for os.popen()'s default buffering to match that of open() itself which is that they're buffered a buffer size of io.DEFAULT_BUFFER_SIZE.
History
Date User Action Args
2011-03-16 06:03:40gregory.p.smithsetrecipients: + gregory.p.smith, giampaolo.rodola, neologix, rosslagerwall, amicitas
2011-03-16 06:03:40gregory.p.smithsetmessageid: <1300255420.66.0.417319235522.issue11459@psf.upfronthosting.co.za>
2011-03-16 06:03:39gregory.p.smithlinkissue11459 messages
2011-03-16 06:03:39gregory.p.smithcreate