➜

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 <1570245883.54.0.886767259366.issue38373@roundup.psfhosted.org>
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).
History
Date User Action Args
2019-10-05 03:24:43tim.peterssetrecipients: + tim.peters, rhettinger, serhiy.storchaka, brandtbucher
2019-10-05 03:24:43tim.peterssetmessageid: <1570245883.54.0.886767259366.issue38373@roundup.psfhosted.org>
2019-10-05 03:24:43tim.peterslinkissue38373 messages
2019-10-05 03:24:43tim.peterscreate