Corey Coughlin <[EMAIL PROTECTED]> writes:
> Mike Meyer wrote:
>> Calls to methods of a separate object are non-blocking. The calls are
>> queued, and executed later. Reading an attribute from a separate
>> object is a blocking action. Calling a method with a separate object
>> as an argument caus
Mike Meyer wrote:
> [Rest elided]
>
> This really has a lot in common with SCOOP. SCOOP makes concurrent
> stuff easier, but i'm not sure it fits well with Python. I'll describe
> it, on the off chance you may get some ideas from it. See http://archive.eiffel.com/doc/manuals/technology/concurren
[EMAIL PROTECTED] writes:
> Alright, so I've been following some of the arguments about enhancing
> parallelism in python, and I've kind of been struck by how hard things
> still are. It seems like what we really need is a more pythonic
> approach.
I certainly agree, and have thought about it som
OK, thanks for all this criticism, you've obviously taken some time
here, guess I'll see if I can help clear some of this up
Michael wrote:
>
>
> On the surface of it, what you've described resembles Kamaelia[1] -
> specifically in the way used in the Axon Shell [2]. In other ways it
> dif
> Yes. Parallelism certainly deserves attention, and I believe
> "amateurs" are likely to help in the breakthroughs to come. I
> further suspect, though, that they'll be amateurs who benefit
> from knowledge of existing research into the range of documented
> concurrency concepts, including CSPs
Hey, some responses, let's see...
Peter Tillotson wrote:
> I'd really like to see a concurrency system come into python based on
> theories such as Communicating Sequential Processes (CSP) or its
> derivatives lambda or pi calculus. These provide an analytic framework
> for developing multi thr
[EMAIL PROTECTED] wrote:
> Alright, so I've been following some of the arguments about enhancing
> parallelism in python, and I've kind of been struck by how hard things
> still are. It seems like what we really need is a more pythonic
> approach.
[... major snippage ...]
> OK? So what do you a
In article <[EMAIL PROTECTED]>,
Peter Tillotson <[EMAIL PROTECTED]> wrote:
>I'd really like to see a concurrency system come into python based on
>theories such as Communicating Sequential Processes (CSP) or its
>derivatives lambda or pi calculus. These provide an analytic framework
>for develo
I'd really like to see a concurrency system come into python based on
theories such as Communicating Sequential Processes (CSP) or its
derivatives lambda or pi calculus. These provide an analytic framework
for developing multi thread / process apps. CSP like concurrency is one
of the hidden gem
Alright, so I've been following some of the arguments about enhancing
parallelism in python, and I've kind of been struck by how hard things
still are. It seems like what we really need is a more pythonic
approach. One thing I've been seeing suggested a lot lately is that
running jobs in separate
10 matches
Mail list logo
