Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.019 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'parameters': 0.04; 'alternatives': 0.09; 'counting': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'sequences.': 0.09; 'python': 0.11; '*with': 0.16; '12:57': 0.16; 'optional': 0.16; 'pity': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'applies': 0.16; 'wrote:': 0.18; 'code.': 0.18; 'tests': 0.22; 'header:User-Agent:1': 0.23; 'asking': 0.27; 'header:X-Complaints- To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'function': 0.29; 'said,': 0.30; 'start,': 0.30; 'code': 0.31; 'that.': 0.31; 'boundary': 0.31; 'faster,': 0.31; 'forces': 0.31; 'such.': 0.31; 'anyone': 0.31; 'advice': 0.35; 'but': 0.35; 'there': 0.35; 'subject:List': 0.36; 'words,': 0.36; 'done': 0.36; 'doing': 0.36; 'so,': 0.37; 'list.': 0.37; 'performance': 0.37; 'generic': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'rather': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'easy': 0.60; 'is.': 0.60; 'effective': 0.61; 'received:173': 0.61; 'simple': 0.61; 'happen': 0.63; 'more': 0.64; 'within': 0.65; 'between': 0.67; 'results': 0.69; 'limit': 0.70; 'lack': 0.78; 'different.': 0.84; 'received:fios.verizon.net': 0.84; 'substrings': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Jan Reedy Subject: Re: List Count Date: Tue, 23 Apr 2013 16:00:56 -0400 References: <5175377f$0$29977$c3e8da3$5496439d@news.astraweb.com> <517545F7.5090209@nowhere.org> <5175c12f$0$29977$c3e8da3$5496439d@news.astraweb.com> <51769f96$0$29977$c3e8da3$5496439d@news.astraweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-173-75-251-66.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 36 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1366747255 news.xs4all.nl 2255 [2001:888:2000:d::a6]:34921 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:44210 On 4/23/2013 12:57 PM, Blind Anagram wrote: > So, all I was doing in asking for advice was to check whether there is > an easy way of avoiding the slice copy, And there is. > not because this is critical, > but rather because it is a pity to limit the performance because Python > forces a (strictly unnecessary) copy in order to perform a count within > a part of a list. Python does not force that. You have been given several simple no-copy alternatives. They happen to be slower *with CPython* because of the speed difference between Python code and C code. If the same timing tests were done with any of the implementations that execute python code faster, the results would likely be different. I thing str/byte/bytearray.count have more need for optional start,stop boundary parameters because a) people search in long texts and subtexts, more so I think that for other sequences, b) they search for substrings longer than 1 and hence c) the generic no-slice alternatives do not work for counting substrings. That said, I do see that tuple/list.index have had start, stop paramaters added, so doing the same for .count is conceivable. I just do not remember anyone else asking for such. The use case must be very rare. And as I said in my other post, .count(x) applies to any collections, but start,stop would only apply to sequences. > In other words, the lack of a list.count(value, limit) function makes > Python less effective than it would otherwise be. Untrue. The alternatives are just as *effective*.