From 1d8b04edfdc3030e645730492bfcc27b75718b96 Mon Sep 17 00:00:00 2001 From: sgal <32255369+sgalal@users.noreply.github.com> Date: Tue, 16 Jul 2019 08:15:17 -0700 Subject: 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 * Include the removal of the previous line Co-Authored-By: Kyle Stanley * Remove an extra space --- Doc/c-api/long.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Doc/c-api/long.rst b/Doc/c-api/long.rst index fdaefaf..aeebf30 100644 --- a/Doc/c-api/long.rst +++ b/Doc/c-api/long.rst @@ -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) -- cgit v0.12