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-September/038010.html below:

[Python-Dev] Making python C-API thread safe (try 2)

[Python-Dev] Making python C-API thread safe (try 2) [Python-Dev] Making python C-API thread safe (try 2)Brian Quinlan brian at sweetapp.com
Thu Sep 11 12:06:43 EDT 2003
> Making the individual interpreters thread safe is trivial, and
benefits
> many people, 

I'm not sure that I believe this statement. Isn't this of benefit only
to people who want to have multiple interpreter instances running
concurrently in an embedding situation? I doubt that there is an army of
people who want to do that.

> and is a necessary first step; making threads within
> interpreter thread safe is possible as well, at least if you leave
> something for the developer, as you should, as you do in every other
> programming language as well.

Of course it is possible (and would likely be of benefit to more than a
handful of Python users). The problem is that it requires effort, would
likely require massive code breakage and the locking required would
likely significantly decrease Python's single-thread performance.

Cheers,
Brian


More information about the Python-Dev mailing list

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