This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients Ramchandra Apte, casevh, kachayev, mark.dickinson, serhiy.storchaka, skrah
Date 2012-11-17.13:56:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353160600.43.0.879008137081.issue16483@psf.upfronthosting.co.za>
In-reply-to
Content
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
python-ideas.
History
Date User Action Args
2012-11-17 13:56:40skrahsetrecipients: + skrah, mark.dickinson, casevh, Ramchandra Apte, serhiy.storchaka, kachayev
2012-11-17 13:56:40skrahsetmessageid: <1353160600.43.0.879008137081.issue16483@psf.upfronthosting.co.za>
2012-11-17 13:56:40skrahlinkissue16483 messages
2012-11-17 13:56:40skrahcreate