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 ncoghlan
Recipients doerwalter, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-19.14:10:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384870244.85.0.128914371924.issue19619@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a proof of concept for the blacklist approach (for 3.4, but without the fixes needed for the transform codec handling tests in test_codecs)

This does have the potential to add a reasonable amount of additional overhead to encoding and decoding for shortstrings. Since it isn't obvious where to store a set for faster checking against the blacklist, it may be worth benchmarking this naive approach before doing something more complicated.

Regardless, I don't plan to take this further myself any time soon - I just wanted to give it a firm nudge in the direction of the blacklist approach by providing a proof of concept.
History
Date User Action Args
2013-11-19 14:10:44ncoghlansetrecipients: + ncoghlan, lemburg, doerwalter, vstinner, ezio.melotti, serhiy.storchaka
2013-11-19 14:10:44ncoghlansetmessageid: <1384870244.85.0.128914371924.issue19619@psf.upfronthosting.co.za>
2013-11-19 14:10:44ncoghlanlinkissue19619 messages
2013-11-19 14:10:44ncoghlancreate