From 1f8a40b81d359c66b6b67dd0f532a655cf490b68 Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith" Date: Wed, 20 Mar 2013 18:32:03 -0700 Subject: remove the long obsolete mention of universal newlines mode only being available when configured at compile time. --- Lib/subprocess.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'Lib/subprocess.py') diff --git a/Lib/subprocess.py b/Lib/subprocess.py index 1a21455a9b..7cfe5df30d 100644 --- a/Lib/subprocess.py +++ b/Lib/subprocess.py @@ -108,10 +108,9 @@ If universal_newlines is true, the file objects stdout and stderr are opened as a text files, but lines may be terminated by any of '\n', the Unix end-of-line convention, '\r', the old Macintosh convention or '\r\n', the Windows convention. All of these external representations -are seen as '\n' by the Python program. Note: This feature is only -available if Python is built with universal newline support (the -default). Also, the newlines attribute of the file objects stdout, -stdin and stderr are not updated by the communicate() method. +are seen as '\n' by the Python program. Also, the newlines attribute +of the file objects stdout, stdin and stderr are not updated by the +communicate() method. The startupinfo and creationflags, if given, will be passed to the underlying CreateProcess() function. They can specify things such as -- cgit v1.2.1