➜

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 chris.jerdonek
Recipients asvetlov, chris.jerdonek, georg.brandl, gregory.p.smith, pitrou, r.david.murray
Date 2012-08-15.20:38:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345063109.29.0.618404854557.issue12623@psf.upfronthosting.co.za>
In-reply-to
Content 
> Pushing to communicate input with "\r" (see attached patch) produces the error.

Is this a supported use case?  In universal newlines, stdin line endings are supposed to be "\n".  From the subprocess documentation: "For stdin, line ending characters '\n' in the input will be converted to the default line separator os.linesep."
History
Date User Action Args
2012-08-15 20:38:29chris.jerdoneksetrecipients: + chris.jerdonek, georg.brandl, gregory.p.smith, pitrou, r.david.murray, asvetlov
2012-08-15 20:38:29chris.jerdoneksetmessageid: <1345063109.29.0.618404854557.issue12623@psf.upfronthosting.co.za>
2012-08-15 20:38:28chris.jerdoneklinkissue12623 messages
2012-08-15 20:38:28chris.jerdonekcreate