Mailman 3 April 2022 - Python-checkins

codecs docs: fix grammar mistake (GH-29462)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/bf0f04f87139bceac1a5f84326d1a3ed3a… commit: bf0f04f87139bceac1a5f84326d1a3ed3a5c4061 branch: 3.9 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T14:34:18-07:00 summary: codecs docs: fix grammar mistake (GH-29462) (cherry picked from commit ea56845744e815ed468dfbdd835110254c3be997) Co-authored-by: 180909 <wjh180909(a)gmail.com> files: M Doc/library/codecs.rst diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst index 3386208d5ef5f..1a71e5791170d 100644 --- a/Doc/library/codecs.rst +++ b/Doc/library/codecs.rst @@ -909,7 +909,7 @@ there's the so called BOM ("Byte Order Mark"). This is the Unicode character ``U+FEFF``. This character can be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte swapped version of this character (``0xFFFE``) is an illegal character that may not appear in a Unicode text. So when the -first character in an ``UTF-16`` or ``UTF-32`` byte sequence +first character in a ``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow

1 0

codecs docs: fix grammar mistake (GH-29462)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/2d936a42ac2b45ddc160eb90178cc9b410… commit: 2d936a42ac2b45ddc160eb90178cc9b4107639db branch: 3.10 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T14:33:52-07:00 summary: codecs docs: fix grammar mistake (GH-29462) (cherry picked from commit ea56845744e815ed468dfbdd835110254c3be997) Co-authored-by: 180909 <wjh180909(a)gmail.com> files: M Doc/library/codecs.rst diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst index 1a1ce9237b010..9e2eb63479282 100644 --- a/Doc/library/codecs.rst +++ b/Doc/library/codecs.rst @@ -912,7 +912,7 @@ there's the so called BOM ("Byte Order Mark"). This is the Unicode character ``U+FEFF``. This character can be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte swapped version of this character (``0xFFFE``) is an illegal character that may not appear in a Unicode text. So when the -first character in an ``UTF-16`` or ``UTF-32`` byte sequence +first character in a ``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow

1 0

bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/dc9322a91d48c80afe8329bb509673a2f7… commit: dc9322a91d48c80afe8329bb509673a2f74fb925 branch: 3.9 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T14:21:45-07:00 summary: bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845) (cherry picked from commit c93a0ac6972221787d8bea1c41a9feb667ed3d2c) Co-authored-by: 180909 <wjh180909(a)gmail.com> files: M Doc/library/stat.rst diff --git a/Doc/library/stat.rst b/Doc/library/stat.rst index 98219eaee9761..083dc5e3bcfd6 100644 --- a/Doc/library/stat.rst +++ b/Doc/library/stat.rst @@ -109,7 +109,7 @@ Example:: for f in os.listdir(top): pathname = os.path.join(top, f) - mode = os.stat(pathname).st_mode + mode = os.lstat(pathname).st_mode if S_ISDIR(mode): # It's a directory, recurse into it walktree(pathname, callback)

1 0

bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/23c0200c436714a3f9b38d5e6cac230cea… commit: 23c0200c436714a3f9b38d5e6cac230ceacd4c43 branch: 3.10 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T14:19:48-07:00 summary: bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845) (cherry picked from commit c93a0ac6972221787d8bea1c41a9feb667ed3d2c) Co-authored-by: 180909 <wjh180909(a)gmail.com> files: M Doc/library/stat.rst diff --git a/Doc/library/stat.rst b/Doc/library/stat.rst index 98219eaee9761..083dc5e3bcfd6 100644 --- a/Doc/library/stat.rst +++ b/Doc/library/stat.rst @@ -109,7 +109,7 @@ Example:: for f in os.listdir(top): pathname = os.path.join(top, f) - mode = os.stat(pathname).st_mode + mode = os.lstat(pathname).st_mode if S_ISDIR(mode): # It's a directory, recurse into it walktree(pathname, callback)

1 0

codecs docs: fix grammar mistake (GH-29462)
by JelleZijlstra April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/ea56845744e815ed468dfbdd835110254c… commit: ea56845744e815ed468dfbdd835110254c3be997 branch: main author: 180909 <wjh180909(a)gmail.com> committer: JelleZijlstra <jelle.zijlstra(a)gmail.com> date: 2022-04-02T14:12:32-07:00 summary: codecs docs: fix grammar mistake (GH-29462) files: M Doc/library/codecs.rst diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst index 76710974dd427..e6f5954d33b59 100644 --- a/Doc/library/codecs.rst +++ b/Doc/library/codecs.rst @@ -915,7 +915,7 @@ there's the so called BOM ("Byte Order Mark"). This is the Unicode character ``U+FEFF``. This character can be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte swapped version of this character (``0xFFFE``) is an illegal character that may not appear in a Unicode text. So when the -first character in an ``UTF-16`` or ``UTF-32`` byte sequence +first character in a ``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow

1 0

bpo-46315: Use fopencookie only on Emscripten 3.x and newer (GH-32266)
by tiran April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/3df0e63aabef905b72fad78256f24b9270… commit: 3df0e63aabef905b72fad78256f24b9270c63172 branch: main author: Christian Heimes <christian(a)python.org> committer: tiran <christian(a)python.org> date: 2022-04-02T23:11:38+02:00 summary: bpo-46315: Use fopencookie only on Emscripten 3.x and newer (GH-32266) files: M Parser/tokenizer.c diff --git a/Parser/tokenizer.c b/Parser/tokenizer.c index 13116d052ea59..db84e2e92e167 100644 --- a/Parser/tokenizer.c +++ b/Parser/tokenizer.c @@ -2072,7 +2072,7 @@ _PyTokenizer_Get(struct tok_state *tok, return result; } -#if defined(__wasi__) || defined(__EMSCRIPTEN__) +#if defined(__wasi__) || (defined(__EMSCRIPTEN__) && (__EMSCRIPTEN_major__ >= 3)) // fdopen() with borrowed fd. WASI does not provide dup() and Emscripten's // dup() emulation with open() is slow. typedef union {

1 0

bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845)
by JelleZijlstra April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/c93a0ac6972221787d8bea1c41a9feb667… commit: c93a0ac6972221787d8bea1c41a9feb667ed3d2c branch: main author: 180909 <wjh180909(a)gmail.com> committer: JelleZijlstra <jelle.zijlstra(a)gmail.com> date: 2022-04-02T13:58:26-07:00 summary: bpo-45114: Use lstat() instead of stat() in stat docs example (GH-29845) files: M Doc/library/stat.rst diff --git a/Doc/library/stat.rst b/Doc/library/stat.rst index 98219eaee9761..083dc5e3bcfd6 100644 --- a/Doc/library/stat.rst +++ b/Doc/library/stat.rst @@ -109,7 +109,7 @@ Example:: for f in os.listdir(top): pathname = os.path.join(top, f) - mode = os.stat(pathname).st_mode + mode = os.lstat(pathname).st_mode if S_ISDIR(mode): # It's a directory, recurse into it walktree(pathname, callback)

1 0

bpo-47031: Improve documentation for `math.nan` (GH-32170)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/5b80031fb0d2ea14f0d42a33309ce5464c… commit: 5b80031fb0d2ea14f0d42a33309ce5464c4a6042 branch: 3.9 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T13:23:26-07:00 summary: bpo-47031: Improve documentation for `math.nan` (GH-32170) Co-authored-by: Jelle Zijlstra <jelle.zijlstra(a)gmail.com> (cherry picked from commit 182e93c3f57b0c72e765c9896066d32e461c0865) Co-authored-by: Charlie Zhao <zhaoyu_hit(a)qq.com> files: M Doc/library/math.rst diff --git a/Doc/library/math.rst b/Doc/library/math.rst index b20e557b5c610..9783e9ef825d5 100644 --- a/Doc/library/math.rst +++ b/Doc/library/math.rst @@ -622,8 +622,23 @@ Constants .. data:: nan - A floating-point "not a number" (NaN) value. Equivalent to the output of - ``float('nan')``. + A floating-point "not a number" (NaN) value. Equivalent to the output of + ``float('nan')``. Due to the requirements of the `IEEE-754 standard + <https://en.wikipedia.org/wiki/IEEE_754>`_, ``math.nan`` and ``float('nan')`` are + not considered to equal to any other numeric value, including themselves. To check + whether a number is a NaN, use the :func:`isnan` function to test + for NaNs instead of ``is`` or ``==``. + Example:: + + >>> import math + >>> math.nan == math.nan + False + >>> float('nan') == float('nan') + False + >>> math.isnan(math.nan) + True + >>> math.isnan(float('nan')) + True .. versionadded:: 3.5

1 0

bpo-47031: Improve documentation for `math.nan` (GH-32170)
by miss-islington April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/319a70cf99c9866c7fa47deecf04f6ebcf… commit: 319a70cf99c9866c7fa47deecf04f6ebcfe35a54 branch: 3.10 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: miss-islington <31488909+miss-islington(a)users.noreply.github.com> date: 2022-04-02T13:19:20-07:00 summary: bpo-47031: Improve documentation for `math.nan` (GH-32170) Co-authored-by: Jelle Zijlstra <jelle.zijlstra(a)gmail.com> (cherry picked from commit 182e93c3f57b0c72e765c9896066d32e461c0865) Co-authored-by: Charlie Zhao <zhaoyu_hit(a)qq.com> files: M Doc/library/math.rst diff --git a/Doc/library/math.rst b/Doc/library/math.rst index 145bac4966e18..d485ae5c2706a 100644 --- a/Doc/library/math.rst +++ b/Doc/library/math.rst @@ -627,8 +627,23 @@ Constants .. data:: nan - A floating-point "not a number" (NaN) value. Equivalent to the output of - ``float('nan')``. + A floating-point "not a number" (NaN) value. Equivalent to the output of + ``float('nan')``. Due to the requirements of the `IEEE-754 standard + <https://en.wikipedia.org/wiki/IEEE_754>`_, ``math.nan`` and ``float('nan')`` are + not considered to equal to any other numeric value, including themselves. To check + whether a number is a NaN, use the :func:`isnan` function to test + for NaNs instead of ``is`` or ``==``. + Example:: + + >>> import math + >>> math.nan == math.nan + False + >>> float('nan') == float('nan') + False + >>> math.isnan(math.nan) + True + >>> math.isnan(float('nan')) + True .. versionadded:: 3.5

1 0

bpo-47031: Improve documentation for `math.nan` (GH-32170)
by JelleZijlstra April 2, 2022

April 2, 2022

https://github.com/python/cpython/commit/182e93c3f57b0c72e765c9896066d32e46… commit: 182e93c3f57b0c72e765c9896066d32e461c0865 branch: main author: Charlie Zhao <zhaoyu_hit(a)qq.com> committer: JelleZijlstra <jelle.zijlstra(a)gmail.com> date: 2022-04-02T12:58:03-07:00 summary: bpo-47031: Improve documentation for `math.nan` (GH-32170) Co-authored-by: Jelle Zijlstra <jelle.zijlstra(a)gmail.com> files: M Doc/library/math.rst diff --git a/Doc/library/math.rst b/Doc/library/math.rst index bcbcdef51d3fc..c0f9614231912 100644 --- a/Doc/library/math.rst +++ b/Doc/library/math.rst @@ -646,8 +646,23 @@ Constants .. data:: nan - A floating-point "not a number" (NaN) value. Equivalent to the output of - ``float('nan')``. + A floating-point "not a number" (NaN) value. Equivalent to the output of + ``float('nan')``. Due to the requirements of the `IEEE-754 standard + <https://en.wikipedia.org/wiki/IEEE_754>`_, ``math.nan`` and ``float('nan')`` are + not considered to equal to any other numeric value, including themselves. To check + whether a number is a NaN, use the :func:`isnan` function to test + for NaNs instead of ``is`` or ``==``. + Example:: + + >>> import math + >>> math.nan == math.nan + False + >>> float('nan') == float('nan') + False + >>> math.isnan(math.nan) + True + >>> math.isnan(float('nan')) + True .. versionchanged:: 3.11 It is now always available.

1 0