From 098273f5a266128cb7f0ebbb6f34c43c60b18100 Mon Sep 17 00:00:00 2001 From: Mohamed Koubaa Date: Mon, 14 Sep 2020 13:39:41 -0500 Subject: [PATCH] update doc --- Doc/c-api/intro.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/intro.rst b/Doc/c-api/intro.rst index 7ca8693afab79c..af3cf2701e2a33 100644 --- a/Doc/c-api/intro.rst +++ b/Doc/c-api/intro.rst @@ -236,8 +236,8 @@ assignments, scope rules, and argument passing), it is only fitting that they should be represented by a single C type. Almost all Python objects live on the heap: you never declare an automatic or static variable of type :c:type:`PyObject`, only pointer variables of type :c:type:`PyObject*` can be -declared. The sole exception are the type objects; since these must never be -deallocated, they are typically static :c:type:`PyTypeObject` objects. +declared. The sole exception are the type objects; they may be static +:c:type:`PyTypeObject` objects. All Python objects (even Python integers) have a :dfn:`type` and a :dfn:`reference count`. An object's type determines what kind of object it is