➜

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 martin.panter
Recipients Arfrever, Ramchandra Apte, asvetlov, chris.jerdonek, martin.panter, r.david.murray, serhiy.storchaka
Date 2016-06-12.07:35:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465716903.18.0.972752850081.issue15649@psf.upfronthosting.co.za>
In-reply-to
Content 
See also Issue 27273, proposing to use text string input as an indicator to turn on universal_newlines=True in the higher-level functions. I’m not excited by either proposal, but I find the other one a bit more palatable.

IMO allowing text string input to communicate(), but returning byte string outputs would be a bad idea. It would have been better to call the universal_newlines=... flag “text_mode”.
History
Date User Action Args
2016-06-12 07:35:03martin.pantersetrecipients: + martin.panter, Arfrever, r.david.murray, asvetlov, chris.jerdonek, Ramchandra Apte, serhiy.storchaka
2016-06-12 07:35:03martin.pantersetmessageid: <1465716903.18.0.972752850081.issue15649@psf.upfronthosting.co.za>
2016-06-12 07:35:03martin.panterlinkissue15649 messages
2016-06-12 07:35:02martin.pantercreate