[Python-ideas] solving multi-core Python
Nick Coghlan
ncoghlan at gmail.com
Sun Jun 21 14:55:42 CEST 2015
More information about the Python-ideas mailing list
Sun Jun 21 14:55:42 CEST 2015
- Previous message (by thread): [Python-ideas] solving multi-core Python
- Next message (by thread): [Python-ideas] solving multi-core Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 21 June 2015 at 07:42, Eric Snow <ericsnowcurrently at gmail.com> wrote: > tl;dr Let's exploit multiple cores by fixing up subinterpreters, > exposing them in Python, and adding a mechanism to safely share > objects between them. > > This proposal is meant to be a shot over the bow, so to speak. I plan > on putting together a more complete PEP some time in the future, with > content that is more refined along with references to the appropriate > online resources. > > Feedback appreciated! Offers to help even more so! :) For folks interested in more of the background and design trade-offs involved here, with Eric's initial post published, I've now extracted and updated my old answer about the GIL from the Python 3 Q & A page, and turned it into its own article: http://python-notes.curiousefficiency.org/en/latest/python3/multicore_python.html Cheers, Nick. P.S. The entry for the old Q&A answer is still there, but now redirects to the new article: http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_answers.html#but-but-surely-fixing-the-gil-is-more-important-than-fixing-unicode -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-ideas] solving multi-core Python
- Next message (by thread): [Python-ideas] solving multi-core Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list