Chris Jerdonek added the comment: > 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." ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12623> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
