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/2008-December/084416.html below:

[Python-Dev] The endless GIL debate: why not remove thread support instead?

[Python-Dev] The endless GIL debate: why not remove thread support instead? [Python-Dev] The endless GIL debate: why not remove thread support instead?Greg Ewing greg.ewing at canterbury.ac.nz
Thu Dec 18 23:52:34 CET 2008
Paul Moore wrote:
> Do you know if these remaining problems are listed anywhere?

There was a big discussion about this in comp.lang.python
not long ago. Basically all the built-in types and constants
are shared between interpreters, which means you still need
a GIL to stop different interpreters stepping on each other's
toes.

> AIUI,
> certain software (for example mod_python) has been using multiple
> interpreters for a long while now

Multiple interpeters are possible, they're just not completely
independent. Whether this is a problem depends on the reason
you want multiple interpreters. In the Apache case, it's
probably more about providing virtual Python environments than
free-threading between interpreters.

-- 
Greg
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