From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <5d375e920903031515x7b25dc5hd1ced6d098bd02d0@mail.gmail.com> References: <138575260903030352s623807d7p5a3075b1f7a591f6@mail.gmail.com> <3e1162e60903030719v141b41e9ma5fd98c73d8b0e7c@mail.gmail.com> <1236103870.4929.101.camel@goose.sun.com> <3aaafc130903031508v5e4b3d96n2b53677049e086f6@mail.gmail.com> <5d375e920903031515x7b25dc5hd1ced6d098bd02d0@mail.gmail.com> Date: Tue, 3 Mar 2009 18:23:20 -0500 Message-ID: <3aaafc130903031523h1be94cf1ta61e01fd0caab10e@mail.gmail.com> From: "J.R. Mauro" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] threads vs forks Topicbox-Message-UUID: adb0836e-ead4-11e9-9d60-3106f5b1d025 On Tue, Mar 3, 2009 at 6:15 PM, Uriel wrote: > You are off. It is doubtful that the GIL will ever be removed. That's too bad. Things like that just reinforce my view that Python is a ha= ck :( Oh well, back to C... > > But that really isn't the issue, the issue is the lack of a decent > concurrency model, like the one provided by Stackless. > > But apparently one of the things stackless allows is evil recursive > programming, which Guido considers 'confusing' and wont allow in > mainline python (I think another reason is that porting it to jython > and .not would be hard, but I'm not familiar with the details). Concurrency seems to be one of those things that's "too hard" for everyone, and I don't buy it. There's no reason it needs to be as hard as it is. And nevermind the fact that it's not really usable for every (or even most) jobs out there. But Intel is pushing it, so that's where we have to go, I suppose. > > uriel > - Show quoted text - > > On Wed, Mar 4, 2009 at 12:08 AM, J.R. Mauro wrote: >> On Tue, Mar 3, 2009 at 1:11 PM, Roman V. Shaposhnik wrote: >>> On Tue, 2009-03-03 at 07:19 -0800, David Leimbach wrote: >>> >>>> My knowledge on this subject is about 8 or 9 years old, so check with = your local Python guru.... >>>> >>>> >>>> The last I'd heard about Python's threading is that it was cooperative >>>> only, and that you couldn't get real parallelism out of it. =A0It serv= es >>>> as a means to organize your program in a concurrent manner. >>>> >>>> >>>> In other words no two threads run at the same time in Python, even if >>>> you're on a multi-core system, due to something they call a "Global >>>> Interpreter Lock". >>> >>> I believe GIL is as present in Python nowadays as ever. On a related >>> note: does anybody know any sane interpreted languages with a decent >>> threading model to go along? Stackless python is the only thing that >>> I'm familiar with in that department. >> >> I thought part of the reason for the "big break" with Python 3000 was >> to get rid of the GIL and clean that threading mess up. Or am I way >> off? >> >>> >>> Thanks, >>> Roman. >>> >>> >>> >> >> > >