From: Georg Brandl <georg@python.org>
Date: Mon, 25 Nov 2013 07:48:37 +0000 (+0100)
Subject: Closes #19622: clarify message about bufsize changes in 3.2.4 and 3.3.1.
X-Git-Tag: v3.4.0b2~496^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=37b70bb908261778eec7d074f2ea6e558508f738;p=thirdparty%2FPython%2Fcpython.git

Closes #19622: clarify message about bufsize changes in 3.2.4 and 3.3.1.
---

diff --git a/Doc/library/subprocess.rst b/Doc/library/subprocess.rst
index 49a365775f67..6e67eba5c056 100644
--- a/Doc/library/subprocess.rst
+++ b/Doc/library/subprocess.rst
@@ -441,13 +441,13 @@ functions.
    approximately that size.  A negative bufsize (the default) means
    the system default of io.DEFAULT_BUFFER_SIZE will be used.
 
-   .. versionchanged:: 3.2.4, 3.3.1
+   .. versionchanged:: 3.3.1
 
       *bufsize* now defaults to -1 to enable buffering by default to match the
-      behavior that most code expects.  In 3.2.0 through 3.2.3 and 3.3.0 it
-      incorrectly defaulted to :const:`0` which was unbuffered and allowed
-      short reads.  This was unintentional and did not match the behavior of
-      Python 2 as most code expected.
+      behavior that most code expects.  In versions prior to Python 3.2.4 and
+      3.3.1 it incorrectly defaulted to :const:`0` which was unbuffered
+      and allowed short reads.  This was unintentional and did not match the
+      behavior of Python 2 as most code expected.
 
    The *executable* argument specifies a replacement program to execute.   It
    is very seldom needed.  When ``shell=False``, *executable* replaces the