From 80763d24cfcb79bf925441e22f74df8c71d1735b Mon Sep 17 00:00:00 2001 From: RayXu Date: Mon, 16 Mar 2026 16:21:49 +0800 Subject: [PATCH] Docs: fix a form error and a grammatical error in float.rst (GH-140989) (cherry picked from commit 70397fd1030c310d4d80beeb9c0d88f40c9abed8) Co-authored-by: RayXu --- Doc/c-api/float.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/c-api/float.rst b/Doc/c-api/float.rst index 75ea3d819d3819..420f7f9401fcc4 100644 --- a/Doc/c-api/float.rst +++ b/Doc/c-api/float.rst @@ -194,8 +194,8 @@ NaNs (if such things exist on the platform) isn't handled correctly, and attempting to unpack a bytes string containing an IEEE INF or NaN will raise an exception. -Note that NaNs type may not be preserved on IEEE platforms (signaling NaN become -quiet NaN), for example on x86 systems in 32-bit mode. +Note that NaN type may not be preserved on IEEE platforms (signaling NaNs become +quiet NaNs), for example on x86 systems in 32-bit mode. On non-IEEE platforms with more precision, or larger dynamic range, than IEEE 754 supports, not all values can be packed; on non-IEEE platforms with less @@ -209,7 +209,7 @@ Pack functions The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is an :c:expr:`int` argument, non-zero if you want the bytes string in little-endian -format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` ``p+7``), zero if you +format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` and ``p+7``), zero if you want big-endian format (exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN` constant can be used to use the native endian: it is equal to ``1`` on big endian processor, or ``0`` on little endian processor.