[Python-ideas] PEP 554: Stdlib Module to Support Multiple Interpreters in Python Code
Koos Zevenhoven
k7hoven at gmail.com
Tue Sep 12 11:30:09 EDT 2017
More information about the Python-ideas mailing list
Tue Sep 12 11:30:09 EDT 2017
- Previous message (by thread): [Python-ideas] PEP 554: Stdlib Module to Support Multiple Interpreters in Python Code
- Next message (by thread): [Python-ideas] PEP 554: Stdlib Module to Support Multiple Interpreters in Python Code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Sep 12, 2017 at 5:53 PM, Stefan Krah <stefan at bytereef.org> wrote: > On Tue, Sep 12, 2017 at 05:35:34PM +0300, Koos Zevenhoven wrote: > > I don't see how the situation benefits from calling something the "main > > interpreter". Subinterpreters can be a way to take something > > non-thread-safe and make it thread-safe, because in an > > interpreter-per-thread scheme, most of the state, like module globals, > are > > thread-local. (Well, this doesn't help for async concurrency, but > anyway.) > > You could have a privileged C extension that is only imported in the main > interpreter: > > > if get_current_interp() is main_interp(): > from _decimal import * > else: > from _pydecimal import * > > > Or it could be first-come first-served: if is_imported_by_other_process("_decimal"): from _pydecimal import * else from _decimal import * ––Koos -- + Koos Zevenhoven + http://twitter.com/k7hoven + -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-ideas/attachments/20170912/a031ec6a/attachment.html>
- Previous message (by thread): [Python-ideas] PEP 554: Stdlib Module to Support Multiple Interpreters in Python Code
- Next message (by thread): [Python-ideas] PEP 554: Stdlib Module to Support Multiple Interpreters in Python Code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list