summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2008-03-08 10:05:24 (GMT)
committerGeorg Brandl <georg@python.org>2008-03-08 10:05:24 (GMT)
commit372d55e3e6fb163f7561403b312d9104a7f9238a (patch)
treefda5149c3471cadbfdde98268dd9f4fbda7c7307
parent50967bdec2d0f1511c5ce9590f121ec6d6dde080 (diff)
downloadcpython-372d55e3e6fb163f7561403b312d9104a7f9238a.zip
cpython-372d55e3e6fb163f7561403b312d9104a7f9238a.tar.gz
cpython-372d55e3e6fb163f7561403b312d9104a7f9238a.tar.bz2
#1533486: fix types in refcount intro.
-rw-r--r--Doc/c-api/intro.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/c-api/intro.rst b/Doc/c-api/intro.rst
index 5e9f525..9befaf7 100644
--- a/Doc/c-api/intro.rst
+++ b/Doc/c-api/intro.rst
@@ -137,7 +137,7 @@ reference counts for other objects contained in the object if this is a compound
object type, such as a list, as well as performing any additional finalization
that's needed. There's no chance that the reference count can overflow; at
least as many bits are used to hold the reference count as there are distinct
-memory locations in virtual memory (assuming ``sizeof(long) >= sizeof(char*)``).
+memory locations in virtual memory (assuming ``sizeof(Py_ssize_t) >= sizeof(void*)``).
Thus, the reference count increment is a simple operation.
It is not necessary to increment an object's reference count for every local