➜

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 bkline, dmalcolm, eli.bendersky, flox, kaifeng, neologix, pitrou, python-dev, tim.peters, vstinner
Date 2018-01-16.09:11:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516093898.4.0.467229070634.issue11849@psf.upfronthosting.co.za>
In-reply-to
Content 
Well, memory fragmentation can happen with any allocation scheme, and it's possible even Python 3 isn't immune to this.  Backporting performance improvements is a strain on our resources and also constitutes a maintenance threat (what if the bug hides in the new code?).  And Python 2.7 is really nearing its end-of-life more and more everyday.  So IMHO it's a no-no.
History
Date User Action Args
2018-01-16 09:11:38pitrousetrecipients: + pitrou, tim.peters, vstinner, bkline, eli.bendersky, flox, dmalcolm, neologix, python-dev, kaifeng
2018-01-16 09:11:38pitrousetmessageid: <1516093898.4.0.467229070634.issue11849@psf.upfronthosting.co.za>
2018-01-16 09:11:38pitroulinkissue11849 messages
2018-01-16 09:11:38pitroucreate