[BangPypers] Ideas for Python concurrency...

[Dhananjay Nene]

On Tue, Feb 8, 2011 at 2:15 PM, Vishal <vsapre80 at gmail.com> wrote:

> On Tue, Feb 8, 2011 at 2:10 PM, Baishampayan Ghose <b.ghose at gmail.com
> >wrote:
>
> > > Mutliprocessing means, data copying, talking to each other through
> PIPES,
> > > also it has its issues with running on Windows (all function calls
> should
> > be pickelable)
> > >
> > > Threads seems pretty stable on most platforms where Python runs.
> >
> > Threads won't help you much because of the Python GIL.
> >
> > Regards,
> > BG
> >
> > --
> > Baishampayan Ghose
> > b.ghose at gmail.com
> > '
> >
>
> The GIL is only limited to one interpreter. GIL comes into picture because
> Threads in python create a new interpreter context, so the same interpreter
> switches to new byte codes. The original idea was to create a new
> interpreter for each thread, each one with its own GIL !!!. All within the
> same process.
>

Interesting. But that does raise some curious issues of sharing data across
interpreters.
So as per the original thought - would threads be able to access data across
multiple
interpreters (to implement shared data), or would they have completely
isolated
data islands via message passing ?

Dhananjay

>
> Vishal
> _______________________________________________
> BangPypers mailing list
> BangPypers at python.org
> http://mail.python.org/mailman/listinfo/bangpypers
>