global interpreter lock not working as it should

Michael Hudson mwh at python.net
Fri Aug 2 10:19:07 CEST 2002


a-steinhoff at web.de (Armin Steinhoff) writes:

> Michael Hudson <mwh at python.net> wrote in message news:<lklm7qgbc6.fsf at pc150.maths.bris.ac.uk>...
> > a-steinhoff at web.de (Armin Steinhoff) writes:
> > 
> > > The 'problem' is that Python threads are not fully comparable with
> > > system level threads. Python threads are managed (scheduled) at
> > > _interpreter level_!!
> > > 
> > > The important difference is that Python threads can't use e.g.
> > > blocking I/O calls ... a blocking I/O call used in a Python thread
> > > will block the whole interprete!!.
> > 
> > This is just not true.
> 
> Sorry ... your statement is simply wrong.

No, YOU are.

Cheers,
M.

-- 
  In general, I'd recommend injecting LSD directly into your temples,
  Syd-Barret-style, before mucking with Motif's resource framework.
  The former has far lower odds of leading directly to terminal
  insanity.                                            -- Dan Martinez



More information about the Python-list mailing list