Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 43694a5

Browse files
committed
Issue #18668: Further clarify m_size setting for non-negative values
1 parent fb1a7bc commit 43694a5

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

Doc/c-api/module.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -191,10 +191,10 @@ These functions are usually used in the module initialization function.
191191
freed when the module object is deallocated, after the :c:member:`m_free`
192192
function has been called, if present.
193193
194-
Setting ``m_size`` to a positive value specifies the size of the additional
195-
memory required by the module. Setting it to ``-1`` means that the module can
196-
not be re-initialized because it has global state. Setting it to ``0`` is
197-
forbidden.
194+
Setting ``m_size`` to ``-1`` means that the module can not be
195+
re-initialized because it has global state. Setting it to a non-negative
196+
value means that the module can be re-initialized and specifies the
197+
additional amount of memory it requires for its state.
198198
199199
See :PEP:`3121` for more details.
200200

0 commit comments

Comments
 (0)