Skip to content

Docs: fix a form error and a grammatical error in float.rst #140989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+2 −2
Open

Docs: fix a form error and a grammatical error in float.rst #140989

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
891f667
Docs: fix a form error and a grammatical error in float.rst
F18-Maverick Nov 4, 2025
e159f96
Merge branch 'main' into fix-doc-issue-float.rst
F18-Maverick Nov 10, 2025
c1cd87a
Fix NaN type preservation wording in float.rst
F18-Maverick Nov 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Doc/c-api/float.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@
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
Note that NaN type may not be preserved on IEEE platforms (signaling NaN become
quiet NaN), for example on x86 systems in 32-bit mode.

On non-IEEE platforms with more precision, or larger dynamic range, than IEEE
Expand All @@ -126,9 +126,9 @@
Pack functions
^^^^^^^^^^^^^^

The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is an

Check warning on line 129 in Doc/c-api/float.rst

View workflow job for this annotation

GitHub Actions / Docs / Docs 

c:macro reference target not found: PY_BIG_ENDIAN [ref.macro]
: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
Copy link
Contributor

@skirpichev skirpichev Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` and ``p+7``), zero if you
format (exponent last, at ``p+1``, ``p+3``, or ``p+6``, ``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.
Expand Down
Loading