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 xiang.zhang
Recipients berker.peksag, serhiy.storchaka, twouters, xiang.zhang, ztane
Date 2016-04-29.08:04:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461917071.75.0.338269612581.issue26358@psf.upfronthosting.co.za>
In-reply-to
Content
Although Serhiy thinks we need a separate class for this but I still want to upload my patch first. Maybe some of it can be helpful later, or garbage.

I add a mmap_contains to fix the in operator's behaviour (I don't find the separate issue). I use the simplest search method which is O(m*n). Previously I thought it is not acceptable but I find out that mmap_gfind goes this way too.

By the way, only operations related to mmap_item are affected, which I can see is iteration and in (search does not need to iterate since there is find method), indexing is not affected. So maybe this does not break the backward compatibility that hard.

Hope no disturb.
History
Date User Action Args
2016-04-29 08:04:31xiang.zhangsetrecipients: + xiang.zhang, twouters, berker.peksag, serhiy.storchaka, ztane
2016-04-29 08:04:31xiang.zhangsetmessageid: <1461917071.75.0.338269612581.issue26358@psf.upfronthosting.co.za>
2016-04-29 08:04:31xiang.zhanglinkissue26358 messages
2016-04-29 08:04:31xiang.zhangcreate