A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-February/032963.html below:

Simplified Global Interpreter Lock acquisition for extensions

[Python-Dev] PEP Draft: Simplified Global Interpreter Lock acquisition for extensions [Python-Dev] PEP Draft: Simplified Global Interpreter Lock acquisition for extensionsBrett Cannon bac@OCF.Berkeley.EDU
Tue, 4 Feb 2003 20:50:35 -0800 (PST)
[Mark Hammond]

> Hi all,
>   Following the thread of a couple of months ago, I have prepared a first
> draft of a PEP.  There is still more detail to be filled in the
> "implementation" area, but I would still like feedback on all other areas.
>

Overall I think it is a good PEP (this is coming from someone with hardly
any extension work under his belt and *no* threading work in C under his
belt).

The only point I would make is that in the discussion of
Py_BEGIN_ALLOW_THREADS does not mention any specific drawbacks about it.
Obviously you can draw some since you state they are macros, but if you
do not pick up on that you might not see what so is bad about other than
you say it is for anything complex.  Might just quickly say that it can't
tell whether the interpreter has started or not just like PyThreadState.

-Brett



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