On Jan 14, 2008 11:15 AM, Leif Walsh <[EMAIL PROTECTED]> wrote: > On Jan 14, 2008 1:21 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > How about dropping empty() and full(), but keeping qsize()? empty() is > > trivially rephrased as qsize()==0; I haven't heard any use cases for > > full(). > > I think the point is that, with multiple threads, those methods are > not guaranteed to be correct, whereas trapping the exceptions > apparently are, and therefore, leaving those methods in is confusing > to new programmers who might assume they work and use them without a > second thought.
I'm not sure people who ignore the big "Because of multithreading semantics, this is not reliable" warnings should be catered to. Since others have contributed use-cases for qsize()'s advisory information, it should probably stay around. Collin Winter _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
