From: RayXu Date: Mon, 16 Mar 2026 08:21:49 +0000 (+0800) Subject: Docs: fix a form error and a grammatical error in float.rst (#140989) X-Git-Tag: v3.15.0a8~298 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=70397fd1030c310d4d80beeb9c0d88f40c9abed8;p=thirdparty%2FPython%2Fcpython.git Docs: fix a form error and a grammatical error in float.rst (#140989) --- diff --git a/Doc/c-api/float.rst b/Doc/c-api/float.rst index ca8d44c25c1e..6e83e01344a9 100644 --- a/Doc/c-api/float.rst +++ b/Doc/c-api/float.rst @@ -201,8 +201,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 @@ -216,7 +216,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.