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 martin.panter
Recipients mark.dickinson, martin.panter, rhettinger, tim.peters, xiang.zhang
Date 2016-08-02.01:22:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470100948.06.0.695609170042.issue27662@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like PyMem_RESIZE() would be a truer equivalent than PyMem_Calloc(), since PyMem_MALLOC() does not initialize the memory. I would be happy with changing to that if you want.

PyMem_Malloc() has been limited to PY_SSIZE_T_MAX since Issue 2620, although the documentation <https://docs.python.org/3.5/c-api/memory.html#c.PyMem_Malloc> only mentions “size_t”. There is no match for “ssize_t” etc anywhere on that page.
History
Date User Action Args
2016-08-02 01:22:28martin.pantersetrecipients: + martin.panter, tim.peters, rhettinger, mark.dickinson, xiang.zhang
2016-08-02 01:22:28martin.pantersetmessageid: <1470100948.06.0.695609170042.issue27662@psf.upfronthosting.co.za>
2016-08-02 01:22:27martin.panterlinkissue27662 messages
2016-08-02 01:22:26martin.pantercreate