From: Michael Foord <fuzzyman@voidspace.org.uk>
Date: Sun, 13 Sep 2009 16:13:36 +0000 (+0000)
Subject: Change to tutorial wording for reading text / binary files on Windows. Issue #6301.
X-Git-Tag: v2.7a1~554
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=60931a5a580321b4b225bec9e133ed3998eb7d1a;p=thirdparty%2FPython%2Fcpython.git

Change to tutorial wording for reading text / binary files on Windows. Issue #6301.
---

diff --git a/Doc/tutorial/inputoutput.rst b/Doc/tutorial/inputoutput.rst
index 9efbca5b8b0c..0259749ee21c 100644
--- a/Doc/tutorial/inputoutput.rst
+++ b/Doc/tutorial/inputoutput.rst
@@ -248,8 +248,8 @@ writing. The *mode* argument is optional; ``'r'`` will be assumed if it's
 omitted.
 
 On Windows, ``'b'`` appended to the mode opens the file in binary mode, so there
-are also modes like ``'rb'``, ``'wb'``, and ``'r+b'``.  Windows makes a
-distinction between text and binary files; the end-of-line characters in text
+are also modes like ``'rb'``, ``'wb'``, and ``'r+b'``.  Python on Windows makes
+a distinction between text and binary files; the end-of-line characters in text
 files are automatically altered slightly when data is read or written.  This
 behind-the-scenes modification to file data is fine for ASCII text files, but
 it'll corrupt binary data like that in :file:`JPEG` or :file:`EXE` files.  Be