and in the fullness of time, when Python has acquired enough cruft, will it
be Threaded.Threadable.threading.Thread.yield()? :-)

David LeBlanc
Seattle, WA USA

>  -----Original Message-----
>  From: python-list-admin@[...].org
>  [mailto:python-list-admin@[...].org]On Behalf Of Peter Hansen
>  Sent: Tuesday, May 21, 2002 4:58
>  To: python-list@[...].org
>  Subject: Re: Threading unfairness
> 
> 
>  David LeBlanc wrote (top-posting...David, please don't top-post):
>  >
>  > 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.
> 
>  Alternatively, we could use threading.Thread.yield_(), in keeping
>  with the
>  ugly precedent established with unittest.TestCase.assert_() and the
>  recently discussed poplib.POP3.pass_() methods.
> 
>  -Peter
>  --
>  http://mail.python.org/mailman/listinfo/python-list



-- 
http://mail.python.org/mailman/listinfo/python-list