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 mark.dickinson
Recipients mark.dickinson, ncoghlan, vstinner
Date 2014-02-07.11:13:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391771626.38.0.753256596691.issue20539@psf.upfronthosting.co.za>
In-reply-to
Content
> Some others Python functions like str * int raises a MemoryError on overflow.

I have to say that that's always seemed wrong to me: IMO MemoryError should only be raised when we've really run out of memory, or perhaps where the amount of memory we're about to need exceeds all possible limits (e.g., more than 2**63 bytes on a 64-bit system).
History
Date User Action Args
2014-02-07 11:13:46mark.dickinsonsetrecipients: + mark.dickinson, ncoghlan, vstinner
2014-02-07 11:13:46mark.dickinsonsetmessageid: <1391771626.38.0.753256596691.issue20539@psf.upfronthosting.co.za>
2014-02-07 11:13:46mark.dickinsonlinkissue20539 messages
2014-02-07 11:13:46mark.dickinsoncreate