From e44accf1927ef6306e7764f5cd8bb795d2ec6a98 Mon Sep 17 00:00:00 2001 From: Alexey Date: Wed, 7 Feb 2018 02:07:30 +0300 Subject: [PATCH] Fix typo in Include/objimpl.h, the word "has" was missing (GH-5568) It now reads: ...be aware that Python has no control over... (cherry picked from commit 517da1e58f4c489d4b31579852cde5f7113da08e) Co-authored-by: Alexey --- Include/objimpl.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Include/objimpl.h b/Include/objimpl.h index ed9e7a9680668dd..057bb50cbda9e22 100644 --- a/Include/objimpl.h +++ b/Include/objimpl.h @@ -56,7 +56,7 @@ must use the platform malloc heap(s), or shared memory, or C++ local storage or operator new), you must first allocate the object with your custom allocator, then pass its pointer to PyObject_{Init, InitVar} for filling in its Python- specific fields: reference count, type pointer, possibly others. You should -be aware that Python no control over these objects because they don't +be aware that Python has no control over these objects because they don't cooperate with the Python memory manager. Such objects may not be eligible for automatic garbage collection and you have to make sure that they are released accordingly whenever their destructor gets called (cf. the specific