Message 353986 - 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	tim.peters
Recipients	brandtbucher, rhettinger, serhiy.storchaka, tim.peters
Date	2019-10-05.03:24:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
WRT pymalloc, it will always copy on growing resize in this context. A pymalloc pool is dedicated to blocks of the same size class, so if the size class increases (they're 16 bytes apart now), the data must be copied to a different pool (dedicated to blocks of the larger size class).

WRT pymalloc, it will always copy on growing resize in this context.  A pymalloc pool is dedicated to blocks of the same size class, so if the size class increases (they're 16 bytes apart now), the data must be copied to a different pool (dedicated to blocks of the larger size class).

History
Date	User	Action	Args
2019-10-05 03:24:43	tim.peters	set	recipients: + tim.peters, rhettinger, serhiy.storchaka, brandtbucher
2019-10-05 03:24:43	tim.peters	set	messageid: <[email protected]>
2019-10-05 03:24:43	tim.peters	link	issue38373 messages
2019-10-05 03:24:43	tim.peters	create