summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2006-03-27 22:09:16 (GMT)
committerGeorg Brandl <georg@python.org>2006-03-27 22:09:16 (GMT)
commitb6e92c40a97c3bd6ec6420cdd0d21c1d7ef45817 (patch)
treeb7f24d24c789d924bef6d3bd66c991126c1f7961 /Doc
parent02e19975d40fcef39b061c5cf8c3bdfec0877cb4 (diff)
downloadcpython-b6e92c40a97c3bd6ec6420cdd0d21c1d7ef45817.zip
cpython-b6e92c40a97c3bd6ec6420cdd0d21c1d7ef45817.tar.gz
cpython-b6e92c40a97c3bd6ec6420cdd0d21c1d7ef45817.tar.bz2
Document change made to number of preallocated integers.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/api/concrete.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/api/concrete.tex b/Doc/api/concrete.tex
index f82f7c7..cacefb1 100644
--- a/Doc/api/concrete.tex
+++ b/Doc/api/concrete.tex
@@ -156,7 +156,7 @@ There is no \cfunction{PyNone_Check()} function for the same reason.
Create a new integer object with a value of \var{ival}.
The current implementation keeps an array of integer objects for all
- integers between \code{-1} and \code{100}, when you create an int in
+ integers between \code{-5} and \code{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 \code{1}. I
suspect the behaviour of Python in this case is undefined. :-)