Message 184388 - Python tracker

➜

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	detrout, gregory.p.smith, pitrou, r.david.murray
Date	2013-03-17.17:07:34
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAGE7PNJAqaV_xbL6gVD_PDdsskOsg3d22zq3cOmCcHvck1Je=w@mail.gmail.com>
In-reply-to	<1363529306.43.0.284185681602.issue17443@psf.upfronthosting.co.za>

Content
Yes imaplib can be fixed pretty easily and should use buffered IO regardless. I'm pondering if the default behavior of subprocess needs fixing as existing python 2.x code being ported to 3 doesn't expect this changed behavior of the PIPE file objects. It probably does. Thankfully my subprocess32 backport on 2.x doesn't suffer from the problem as it still uses os.fdopen.

Yes imaplib can be fixed pretty easily and should use buffered IO regardless.

I'm pondering if the default behavior of subprocess needs fixing as
existing python 2.x code being ported to 3 doesn't expect this changed
behavior of the PIPE file objects.  It probably does.

Thankfully my subprocess32 backport on 2.x doesn't suffer from the
problem as it still uses os.fdopen.

History
Date	User	Action	Args
2013-03-17 17:07:34	gregory.p.smith	set	recipients: + gregory.p.smith, pitrou, r.david.murray, detrout
2013-03-17 17:07:34	gregory.p.smith	link	issue17443 messages
2013-03-17 17:07:34	gregory.p.smith	create