From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Mon, 9 Aug 2021 14:39:31 +0000 (-0700)
Subject: bpo-44522: Fix inaccurate information in open() function (GH-27650) (GH-27682)
X-Git-Tag: v3.9.7~68
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=037ef8d6d9cc8225d6db0305cee2d8d0ee5bee74;p=thirdparty%2FPython%2Fcpython.git

bpo-44522: Fix inaccurate information in open() function (GH-27650) (GH-27682)

- Use "Low surrogate code units" instead of "Unicode Private Use Area"
(cherry picked from commit b05e9b63fcfcd4bd7a6434fa9f9a7028d12f91c4)

Co-authored-by: meowmeowmeowcat <meowmeowcat1211@gmail.com>
---

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 784bb62e64a1..c5c1c161293f 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1150,9 +1150,9 @@ are always available.  They are listed here in alphabetical order.
    * ``'replace'`` causes a replacement marker (such as ``'?'``) to be inserted
      where there is malformed data.
 
-   * ``'surrogateescape'`` will represent any incorrect bytes as code
-     points in the Unicode Private Use Area ranging from U+DC80 to
-     U+DCFF.  These private code points will then be turned back into
+   * ``'surrogateescape'`` will represent any incorrect bytes as low
+     surrogate code units ranging from U+DC80 to U+DCFF.
+     These surrogate code units will then be turned back into
      the same bytes when the ``surrogateescape`` error handler is used
      when writing data.  This is useful for processing files in an
      unknown encoding.