Stefan Krah added the comment:

I don't particularly like OverflowError in any situation where the
potential overflow is detected *before* it actually happens. This is
another example:

 >>> x = [1]*99999999999999999999
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OverflowError: cannot fit 'int' into an index-sized integer

So I agree that ValueError is more appropriate, but it may not be worth
fixing it. Closing as "won't fix" sounds fine to me.

A general exception cleanup that reduces the number of exceptions that
a user has to remember is tempting, but should probably be discussed on

nosy: +skrah

Python tracker <>
Python-bugs-list mailing list

Reply via email to