Threading unfairness

[David LeBlanc]

hehehe

We'd have to call it thread.giveitup() since, in spite of my arguments to
the contrary, "yield" now has different semantics in Python then in most
other languages/libraries that support the keyword.

David LeBlanc
Seattle, WA USA

> -----Original Message-----
> From: python-list-admin at python.org
> [mailto:python-list-admin at python.org]On Behalf Of James J. Besemer
> Sent: Monday, May 20, 2002 21:43
> To: Peter Hansen
> Cc: python-list at python.org
> Subject: Re: Threading unfairness
>
>
>
> Peter Hansen wrote:
>
> > We had been unthinkingly using time.sleep(0.01) for a while, just
> > kind of blindly using it as a free "yield timeslice".
>
> Too bad there is no such implementation for this useful function.
>
> It'd be great if time.sleep(0) did the job.  Or even better would
> be if there was
> an explicit thread.yield().
>
> --jb
>
> --
> James J. Besemer  503-280-0838 voice
> http://cascade-sys.com  503-280-0375 fax
> mailto:jb at cascade-sys.com
>
>
>
>
> --
> http://mail.python.org/mailman/listinfo/python-list