Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.016
X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'subject:Python': 0.05; 'case.': 0.05; 'raised': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'regression': 0.09; 'bug': 0.10; 'claims,': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'wrote:': 0.17; 'figures': 0.17; 'tracker': 0.20; 'least': 0.25; 'header:In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.28; "d'aprano": 0.29; 'dramatic': 0.29; 'quoting': 0.29; 'steven': 0.29; 'from:addr:yahoo.co.uk': 0.32; 'not.': 0.32; 'anyone': 0.33; 'to:addr:python-list': 0.33; 'similar': 0.35; 'something': 0.35; 'there': 0.35; 'received:org': 0.36; 'but': 0.36; 'should': 0.36; 'does': 0.37; 'subject:: ': 0.38; 'mark': 0.38; 'performance': 0.39; 'to:addr:python.org': 0.39; 'header:Received:5': 0.40; 'think': 0.40; 'your': 0.60; 'skip:n 10': 0.63; 'confirm': 0.64; 'consequences': 0.71; 'hit.': 0.84; 'liberty': 0.84; 'avoided.': 0.91; 'received:2': 0.91; 'results,': 0.91; 'serious': 0.98
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject: Re: Article on the future of Python
Date: Thu, 27 Sep 2012 17:03:30 +0100
References: <mailman.1294.1348560867.27098.python-list@python.org> <mailman.1333.1348581385.27098.python-list@python.org> <k3ssuq$78m$1@reader1.panix.com> <cc2771fd-0b2b-4721-9ae0-657bc722ebad@googlegroups.com> <ef917cfd-43a5-4620-a9b4-1c6934624bc4@googlegroups.com> <5062ad83$0$29997$c3e8da3$5496439d@news.astraweb.com> <693ac61b-b1d3-4192-9e50-5166fd119278@googlegroups.com> <mailman.1420.1348653316.27098.python-list@python.org> <447851a9-bc63-4711-a4e6-bff565e28f1f@googlegroups.com> <mailman.1438.1348669456.27098.python-list@python.org> <2b2d20f5-2807-4a61-b284-8075e900db22@googlegroups.com> <k3v5p5$uuo$1@ger.gmane.org> <mailman.1443.1348672708.27098.python-list@python.org> <mailman.1445.1348674333.27098.python-list@python.org> <50641d6d$0$29997$c3e8da3$5496439d@news.astraweb.com> <k41hqv$5f0$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gmane-NNTP-Posting-Host: host-2-97-73-49.as13285.net
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
In-Reply-To: <k41hqv$5f0$1@ger.gmane.org>
X-Antivirus: avast! (VPS 120927-0, 27/09/2012), Outbound message
X-Antivirus-Status: Clean
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.1491.1348761753.27098.python-list@python.org>
Lines: 26
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1348761753 news.xs4all.nl 6975 [2001:888:2000:d::a6]:37475
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:30301

On 27/09/2012 13:46, Serhiy Storchaka wrote:
> On 27.09.12 12:33, Steven D'Aprano wrote:
>> Nevertheless, I think there is something here. The consequences are
>> nowhere
>> near as dramatic as jmf claims, but it does seem that replace() has
>> taken a
>> serious performance hit. Perhaps it is unavoidable, but perhaps not.
>>
>> If anyone else can confirm similar results, I think this should be
>> raised as
>> a performance regression.
>
> Yes, I confirm, it's a performance regression. It should be avoidable.
> Almost any PEP393 performance regression can be avoided. At least for
> such corner case. Just no one has yet optimized this case.
>
>

I have taken a liberty and raised this on the bug tracker quoting Steven 
D'Aprano's original figures and your response above.

-- 
Cheers.

Mark Lawrence.