A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/1999-June/095526.html below:

[Python-Dev] ActiveState & fork & Perl

[Python-Dev] ActiveState & fork & PerlTim Peters tim_one at email.msn.com
Mon Jun 28 05:13:15 CEST 1999
Moving back in time ...

[GordonM]
> Perhaps Christian's stackless Python would enable green threads...

[Guido]
> This has been suggested before...  While this seems possible at first,
> all blocking I/O calls would have to be redone to pass control to the
> thread scheduler, before this would be useful -- a huge task!

I didn't understand this.  If I/O calls are left alone, and a green thread
hit one, the whole program just sits there waiting for the call to complete,
right?

But if the same thing happens using "real threads" today, the same thing
happens today anyway <wink>.  That is, if a thread doesn't release the
global lock before a blocking call today, the whole program just sits there
etc.

Or do you have some other kind of problem in mind here?

unconvincedly y'rs  - tim




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