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 Jeffrey.Walton, alex, alexandre.vassalotti, deadshort, dmalcolm, donmez, fweimer, jcea, jwilk, loewis, mark.dickinson, martin.panter, matejcik, miss-islington, nnorwitz, pitrou, python-dev, serhiy.storchaka, vstinner, xiang.zhang, ztane
Date 2018-09-12.00:26:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536711982.01.0.0269046726804.issue1621@psf.upfronthosting.co.za>
In-reply-to
Content
> newsize <<= 1; // The largest possible value is PY_SSIZE_T_MAX + 1. 

Previously, there was a explicitly check for error raising  PyErr_NoMemory() on overflow. Now you rely on PyMem_Malloc() to detect the overflow. I'm not sure that it's a good idea.
History
Date User Action Args
2018-09-12 00:26:22vstinnersetrecipients: + vstinner, loewis, nnorwitz, jcea, mark.dickinson, pitrou, alexandre.vassalotti, donmez, matejcik, jwilk, alex, dmalcolm, python-dev, deadshort, martin.panter, serhiy.storchaka, ztane, fweimer, Jeffrey.Walton, xiang.zhang, miss-islington
2018-09-12 00:26:22vstinnersetmessageid: <1536711982.01.0.0269046726804.issue1621@psf.upfronthosting.co.za>
2018-09-12 00:26:22vstinnerlinkissue1621 messages
2018-09-12 00:26:21vstinnercreate