Message 271774 - Python tracker

➜

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	xiang.zhang
Recipients	martin.panter, xiang.zhang
Date	2016-08-01.07:43:09
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1470037390.18.0.139195089898.issue27662@psf.upfronthosting.co.za>
In-reply-to

Content
List_New checks against PY_SIZE_MAX. The upper bound of PyMem_Malloc is PY_SSIZE_T_MAX. Instead of simply changing the constant, another method is delegating overflow check to PyMem_Calloc, so we can avoid the check in unnecessary check in PyMem_Malloc. But I am not sure hiding the check in PyMem_Calloc is a good idea or not.

List_New checks against PY_SIZE_MAX. The upper bound of PyMem_Malloc is PY_SSIZE_T_MAX.

Instead of simply changing the constant, another method is delegating overflow check to PyMem_Calloc, so we can avoid the check in unnecessary check in PyMem_Malloc. But I am not sure hiding the check in PyMem_Calloc is a good idea or not.

History
Date	User	Action	Args
2016-08-01 07:43:10	xiang.zhang	set	recipients: + xiang.zhang, martin.panter
2016-08-01 07:43:10	xiang.zhang	set	messageid: <1470037390.18.0.139195089898.issue27662@psf.upfronthosting.co.za>
2016-08-01 07:43:09	xiang.zhang	link	issue27662 messages
2016-08-01 07:43:09	xiang.zhang	create