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 vstinner
Recipients serhiy.storchaka, vstinner, xdegaye
Date 2017-06-26.13:15:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498482902.63.0.892188011047.issue30695@psf.upfronthosting.co.za>
In-reply-to
Content
I prefer your new PR. But is it useful to test N memory allocation failures in a row? The API and the code would be simpler if we would only test a single failure. What do you think?

I know that pyfailmalloc is different, but I'm not sure that pyfailmalloc design is right neither :-)
History
Date User Action Args
2017-06-26 13:15:02vstinnersetrecipients: + vstinner, xdegaye, serhiy.storchaka
2017-06-26 13:15:02vstinnersetmessageid: <1498482902.63.0.892188011047.issue30695@psf.upfronthosting.co.za>
2017-06-26 13:15:02vstinnerlinkissue30695 messages
2017-06-26 13:15:02vstinnercreate