From: Eli Bendersky <eliben@gmail.com>
Date: Sat, 10 Aug 2013 12:57:27 +0000 (-0700)
Subject: Issue #18668: Further clarify m_size setting for non-negative values
X-Git-Tag: v3.4.0a2~270^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=43694a50ab5f0083d8d252018739caf2cf4f08d5;p=python

Issue #18668: Further clarify m_size setting for non-negative values
---

diff --git a/Doc/c-api/module.rst b/Doc/c-api/module.rst
index 745b396638..e80e0eaa08 100644
--- a/Doc/c-api/module.rst
+++ b/Doc/c-api/module.rst
@@ -191,10 +191,10 @@ These functions are usually used in the module initialization function.
       freed when the module object is deallocated, after the :c:member:`m_free`
       function has been called, if present.
 
-      Setting ``m_size`` to a positive value specifies the size of the additional
-      memory required by the module. Setting it to ``-1`` means that the module can
-      not be re-initialized because it has global state. Setting it to ``0`` is
-      forbidden.
+      Setting ``m_size`` to ``-1`` means that the module can not be
+      re-initialized because it has global state. Setting it to a non-negative
+      value means that the module can be re-initialized and specifies the
+      additional amount of memory it requires for its state.
 
       See :PEP:`3121` for more details.