➜

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 pitrou
Recipients Yury.Selivanov, alecsandru.patrascu, catalin.manciu, jtaylor, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov
Date 2016-03-09.17:13:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <56E059B0.3000809@free.fr>
In-reply-to <1457542885.21.0.48616790922.issue26249@psf.upfronthosting.co.za>
Content 
Le 09/03/2016 18:01, STINNER Victor a écrit :
> I don't understand why we should keep a slow allocator if Python has a faster allocator?

Define "slow".  malloc() on Linux should be reasonably fast.

Do you think it's reasonable to risk breaking external libraries just
for a hypothetic "performance improvement"?

Again, why don't you try simply changing internal calls?
History
Date User Action Args
2016-03-09 17:13:22pitrousetrecipients: + pitrou, rhettinger, vstinner, Yury.Selivanov, jtaylor, serhiy.storchaka, yselivanov, alecsandru.patrascu, catalin.manciu
2016-03-09 17:13:22pitroulinkissue26249 messages
2016-03-09 17:13:22pitroucreate