From 60931a5a580321b4b225bec9e133ed3998eb7d1a Mon Sep 17 00:00:00 2001 From: Michael Foord Date: Sun, 13 Sep 2009 16:13:36 +0000 Subject: [PATCH] Change to tutorial wording for reading text / binary files on Windows. Issue #6301. --- Doc/tutorial/inputoutput.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/tutorial/inputoutput.rst b/Doc/tutorial/inputoutput.rst index 9efbca5b8b0..0259749ee21 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