Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109244.html below:

[Python-Dev] [Python-checkins] cpython (3.2): Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize()

• Previous message: [Python-Dev] pydoc for named tuples is missing methods
• Next message: [Python-Dev] cpython (3.2): Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

Cheers,
Nick.

-
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

• Previous message: [Python-Dev] pydoc for named tuples is missing methods
• Next message: [Python-Dev] cpython (3.2): Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4