A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045149.html below:

[Python-Dev] Stackless Python

[Python-Dev] Stackless Python [Python-Dev] Stackless PythonGuido van Rossum guido at python.org
Wed Jun 2 13:50:54 EDT 2004
> > Bob Ippolito wrote:
> >>> However, JCSP uses java.lang.Threads to implement
> >>> concurrency. So they are completely unlike Stackless' tasklets
> >>> in their implementation strategy.
> >> So what, if the API is the same?

> In my quick attempt to do CSP on top of CPython threads I learned that:
> - It's not as easy as it sounds to get deterministic behavior out of
>   threads, and debugging threaded python apps is no fun.
> - When it does work, the performance sucks compared to Stackless.

The same is probably true for JCSP.  I don't want a feature that can
only be implemented efficiently by using assembler or some other
platform-specific hack (and most uses of longjmp() fall in that
category, despite its status as an ISO standard library function!).
Especially if the proponents keep using efficiency as the most
important property of the feature.

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4