Skip to content

Commit 1d8b04e

Browse files
sgalalrhettinger
authored andcommitted
bpo-37599: Remove a vague statement in documentation of Integer Objects (#14786)
* Remove a vague statement in documentation * Remove another vague sentence A sentence starting with "So it should be possible..." shouldn't be in the docs either. Co-Authored-By: Kyle Stanley <aeros167@gmail.com> * Include the removal of the previous line Co-Authored-By: Kyle Stanley <aeros167@gmail.com> * Remove an extra space
1 parent a0f7119 commit 1d8b04e

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

Doc/c-api/long.rst

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,9 +42,7 @@ distinguished from a number. Use :c:func:`PyErr_Occurred` to disambiguate.
4242
4343
The current implementation keeps an array of integer objects for all integers
4444
between ``-5`` and ``256``, when you create an int in that range you actually
45-
just get back a reference to the existing object. So it should be possible to
46-
change the value of ``1``. I suspect the behaviour of Python in this case is
47-
undefined. :-)
45+
just get back a reference to the existing object.
4846
4947
5048
.. c:function:: PyObject* PyLong_FromUnsignedLong(unsigned long v)

0 commit comments

Comments
 (0)