From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Fri, 7 Oct 2022 18:21:01 +0000 (-0700)
Subject: gh-64921: Clarify wording for open()'s newline arg (GH-96171)
X-Git-Tag: v3.11.0~120
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=40527c2b1918b7045f9b8b235b4b9e54f9cce91a;p=thirdparty%2FPython%2Fcpython.git

gh-64921: Clarify wording for open()'s newline arg (GH-96171)

(cherry picked from commit 4a74e6ab3885e7906cc5e0b15addc7779bc76249)

Co-authored-by: Stanley <46876382+slateny@users.noreply.github.com>
---

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 4986d0a47e2a..635cffdc0bae 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1267,8 +1267,8 @@ are always available.  They are listed here in alphabetical order.
 
    .. _open-newline-parameter:
 
-   *newline* controls how :term:`universal newlines` mode works (it only
-   applies to text mode).  It can be ``None``, ``''``, ``'\n'``, ``'\r'``, and
+   *newline* determines how to parse newline characters from the stream.
+   It can be ``None``, ``''``, ``'\n'``, ``'\r'``, and
    ``'\r\n'``.  It works as follows:
 
    * When reading input from the stream, if *newline* is ``None``, universal