Path: csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!news.mixmin.net!news2.arglkargh.de!news.wiretrip.org!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'interpreter': 0.05; 'threads,': 0.05; 'python': 0.08; 'subject:removing': 0.09; 'suggestions,': 0.09; 'tue,': 0.12; 'wrote:': 0.14; ':))': 0.16; 'constructs.': 0.16; 'from:addr:awilliam': 0.16; 'from:addr:whitemice.org': 0.16; 'from:name:adam tauno williams': 0.16; 'message-id:@linux-yu4c.site': 0.16; 'parallel,': 0.16; 'received:72.14.190': 0.16; 'received:72.14.190.87': 0.16; 'received:mail.wmmi.net': 0.16; 'received:wmmi.net': 0.16; 'reply- to:addr:awilliam': 0.16; 'reply-to:addr:whitemice.org': 0.16; 'subject:Idea': 0.16; 'x-mailer:evolution 2.30.1.2': 0.16; 'module.': 0.23; 'threads': 0.23; 'header:In-Reply-To:1': 0.23; 'possible,': 0.24; "isn't": 0.26; 'received:72.14': 0.27; 'done.': 0.28; 'process,': 0.28; 'url:library': 0.28; 'assuming': 0.28; 'bound': 0.28; 'to:addr:python-list': 0.31; 'creates': 0.31; 'exactly': 0.32; 'allow': 0.35; 'url:docs': 0.35; 'but': 0.36; 'thread': 0.36; 'two': 0.38; 'works': 0.38; 'similar': 0.38; 'url:org': 0.38; 'subject:: ': 0.39; 'some': 0.39; 'url:python': 0.39; 'header:Mime-Version:1': 0.39; 'to:addr:python.org': 0.40; 'comments,': 0.64; 'today': 0.71; 'reply-to:no real name:2**0': 0.72; 'header:Reply-To:1': 0.72 Subject: Re: Idea for removing the GIL... From: Adam Tauno Williams To: python-list@python.org In-Reply-To: <7d3a67ba-b5ff-4b11-95b5-71f041dfc63a@o7g2000prn.googlegroups.com> References: <7d3a67ba-b5ff-4b11-95b5-71f041dfc63a@o7g2000prn.googlegroups.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 08 Feb 2011 05:05:05 -0500 Mime-Version: 1.0 X-Mailer: Evolution 2.30.1.2 Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: awilliam@whitemice.org List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 16 NNTP-Posting-Host: 82.94.164.166 X-Trace: 1297159531 news.xs4all.nl 81485 [::ffff:82.94.164.166]:59035 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:55519 On Tue, 2011-02-08 at 01:39 -0800, Vishal wrote: > Is it possible that the Python process, creates copies of the > interpreter for each thread that is launched, and some how the thread > is bound to its own interpreter ? > and it "may" also allow the two threads to run in parallel, assuming > the processors of today can send independent instructions from the > same process to multiple cores? > Comments, suggestions, brush offs are welcome :)) Yes, it is possible, and done. See the multiprocessing module. It works very well. It isn't exactly the same as threads, but provides many similar constructs.