[Python-checkins] bpo-37599: Remove a vague statement in documentation of Integer Objects (#14786)

[Raymond Hettinger]

https://github.com/python/cpython/commit/1d8b04edfdc3030e645730492bfcc27b75718b96
commit: 1d8b04edfdc3030e645730492bfcc27b75718b96
branch: master
author: sgal <32255369+sgalal at users.noreply.github.com>
committer: Raymond Hettinger <rhettinger at users.noreply.github.com>
date: 2019-07-16T08:15:17-07:00
summary:

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 at gmail.com>

* Include the removal of the previous line

Co-Authored-By: Kyle Stanley <aeros167 at gmail.com>

* Remove an extra space

files:
M Doc/c-api/long.rst

diff --git a/Doc/c-api/long.rst b/Doc/c-api/long.rst
index fdaefafe21ba..aeebf3060eb4 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)