[Python-Dev] cpython (3.2): Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize()
Antoine Pitrou
solipsis at pitrou.net
Mon Mar 14 12:47:25 CET 2011
On Mon, 14 Mar 2011 06:01:17 -0400
Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Sun, Mar 13, 2011 at 6:29 PM, antoine.pitrou
> <python-checkins at python.org> wrote:
> > .. index:: single: Py_Initialize()
> >
> > - This is a no-op when called for a second time. It is safe to call this function
> > - before calling :c:func:`Py_Initialize`.
> > + This is a no-op when called for a second time.
>
> This change probably deserves a "versionchanged" tag and a note in the
> "Porting to Python 3" section of What's New, since it may cause
> weirdness for people embedding Python in their apps.
Agreed, will do.
cheers
Antoine.
More information about the Python-Dev
mailing list