On Tue, Sep 2, 2008 at 12:26 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I stand by my view. I might voice strong discomfort with raising an
> exception because it doesn't fit in some implementation detail.
Isn't that precisely what OverflowError is for? ("it doesn't fit in some
implementation detail")
It seems to me that the Purity angle here would be to allow len() to return
any Python int object. The Practical angle wants to restrict it to
sys.maxsize for performance reasons. Throwing an OverflowError seems like a
good way for Practical to cry, "Oops, I've been caught".
(I'm interested in this issue because my list-like extension
type<http://stutzbachenterprises.com/blist>can in some cases have a
length greater than sys.maxsize)
--
Daniel Stutzbach, Ph.D.
http://stutzbachenterprises.com
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
