[Stackless] Stackless support for IO.

Richard Tew richard.m.tew at gmail.com
Sat Mar 1 00:00:50 CET 2014

I think it's better to keep Stackless itself as simple and
straightforward as possible, for what it is.

There's no reason to complicate things with a framework that can't
handle every possible blocking case which might come up anyway.


On 2/28/14, Piotr Husiatyński <piotrhusiatynski at gmail.com> wrote:
> Hi,
> I'm considering using stackless for my project, but one thing bothers
> me. Stackless provides tools for creating light threads and comunicate
> between them, which are used to build concurent applications. This
> often involves a lot of IO opperations. But there's no native support
> for blockingoperations. Instead, suggested solution is to use library
> that does that and use stackless on top of it.
> I'm trying to understand why stackless does not provide any support
> for nonblocking IO operations. What is the reason for not having
> internal main loop that take care or blocking operations and blocking
> system calls switching by default?
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless

More information about the Stackless mailing list