8000 gh-100428: Make int documentation more accurate by hauntsaninja · Pull Request #100436 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

gh-100428: Make int documentation more accurate #100436

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.

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

Merged
merged 5 commits into from
Jan 2, 2023
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
add missing word
  • Loading branch information
hauntsaninja committed Jan 2, 2023
commit e7ba3a9ba10a2aeccbee13a2b4068800a3c00c62
6 changes: 3 additions & 3 deletions Doc/library/functions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -901,9 +901,9 @@ are always available. They are listed here in alphabetical order.
default *base* is 10. The allowed bases are 0 and 2--36. Base-2, -8, and -16
strings can be optionally prefixed with ``0b``/``0B``, ``0o``/``0O``, or
``0x``/``0X``, as with integer literals in code. For base 0, the string is
interpreted in a similar to an :ref:`integer literal in code <integers>`, in
that the actual base is 2, 8, 10, or 16 as determined by the prefix. Base 0
also disallows leading zeros: ``int('010', 0)`` is not legal, while
interpreted in a similar way to an :ref:`integer literal in code <integers>`,
in that the actual base is 2, 8, 10, or 16 as determined by the prefix. Base
0 also disallows leading zeros: ``int('010', 0)`` is not legal, while
``int('010')`` and ``int('010', 8)`` are.

The integer type is described in :ref:`typesnumeric`.
Expand Down
0