From 9bb9877d8079ccfc4f5b5448ba111392140112e4 Mon Sep 17 00:00:00 2001 From: Antoine Pitrou Date: Tue, 15 Mar 2011 20:22:50 +0100 Subject: [PATCH] Followup to 4c59cd84086f: add an entry in the porting guide and a "versionchanged" attribute. --- Doc/c-api/init.rst | 5 +++-- Doc/whatsnew/3.2.rst | 4 ++++ 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index 2641c8b7f25..623bd7cea35 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -537,10 +537,11 @@ code, or when embedding the Python interpreter: operations such as ``PyEval_ReleaseThread(tstate)``. It is not needed before calling :c:func:`PyEval_SaveThread` or :c:func:`PyEval_RestoreThread`. - .. index:: single: Py_Initialize() - This is a no-op when called for a second time. + .. versionchanged:: 3.2 + This function cannot be called before :c:func:`Py_Initialize()` anymore. + .. index:: module: _thread .. note:: diff --git a/Doc/whatsnew/3.2.rst b/Doc/whatsnew/3.2.rst index 3829ce14f37..20ce228d514 100644 --- a/Doc/whatsnew/3.2.rst +++ b/Doc/whatsnew/3.2.rst @@ -2698,3 +2698,7 @@ require changes to your code: a new function, :func:`asyncore.handle_accepted`, was added to replace it. (Contributed by Giampaolo Rodola in :issue:`6706`.) + +* Due to the new :term:`GIL` implementation, :c:func:`PyEval_InitThreads()` + cannot be called before :c:func:`Py_Initialize()` anymore. +