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

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?Paul Moore p.f.moore at gmail.com
Thu Dec 18 12:47:37 CET 2008
2008/12/17 Greg Ewing <greg.ewing at canterbury.ac.nz>:
> Nick Coghlan wrote:
>
>> Actually, I believe 3.0 already took a big step towards allowing this by
>> changing the way modules are initialised.
>
> It's a step, but I wouldn't call it a big one. There are
> many other problems to be solved before fully independent
> interpreters are possible.

Do you know if these remaining problems are listed anywhere? AIUI,
certain software (for example mod_python) has been using multiple
interpreters for a long while now - admittedly not without issues, but
certainly enough to imply that multiple interpreters are at least
"possible" - although not perfect. Experience with such software would
probably be a great guide to where the issues exist.

Maybe a page on the Python Wiki, or a FAQ entry, would be useful here.
If only to make things explicit, and clear up some of the FUD around
multiple interpreters.

Paul.
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