Skip to content

bpo-37599: Remove a vague statement in documentation of Integer Objects #14786

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

Merged
merged 4 commits into from
Jul 16, 2019
Merged

bpo-37599: Remove a vague statement in documentation of Integer Objects #14786

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ca63b3d
Remove a vague statement in documentation
sgalal Jul 15, 2019
a16fd4b
Remove another vague sentence
sgalal Jul 16, 2019
7e1dd46
Include the removal of the previous line
sgalal Jul 16, 2019
040c2fd
Remove an extra space
sgalal Jul 16, 2019
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: 1 addition & 3 deletions Doc/c-api/long.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,7 @@ distinguished from a number. Use :c:func:`PyErr_Occurred` to disambiguate.

The current implementation keeps an array of integer objects for all integers
between ``-5`` and ``256``, when you create an int in that range you actually
just get back a reference to the existing object. So it should be possible to
change the value of ``1``. I suspect the behaviour of Python in this case is
undefined. :-)
just get back a reference to the existing object.


.. c:function:: PyObject* PyLong_FromUnsignedLong(unsigned long v)
Expand Down