Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'broken': 0.04; 'from:addr:yahoo.co.uk': 0.04; 'widely': 0.05; 'elements.': 0.07; 'suppose': 0.07; 'arrays': 0.09; 'lawrence': 0.09; 'overflow': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'yeah,': 0.09; 'python': 0.11; 'bug': 0.12; 'language.': 0.14; '"community".': 0.16; 'galaxy': 0.16; 'lengths': 0.16; 'margin': 0.16; 'phones.': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'roy': 0.16; 'so.': 0.16; 'language': 0.16; 'fix': 0.17; 'wrote:': 0.18; 'stack': 0.19; '>>>': 0.22; 'proposed': 0.22; 'header:User-Agent:1': 0.23; 'bytes': 0.24; 'pointer': 0.24; 'guys': 0.24; 'looks': 0.24; 'mention': 0.26; 'header:X -Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'specifically': 0.29; 'fixed': 0.29; 'url:bugs': 0.29; 'originally': 0.30; "i'm": 0.30; 'code': 0.31; 'piece': 0.31; 'url:python': 0.33; 'community': 0.33; 'bugs': 0.33; 'next': 0.36; 'url:org': 0.36; 'url:eu': 0.37; 'wrong': 0.37; 'being': 0.38; 'thank': 0.38; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'how': 0.40; 'most': 0.60; 'devices': 0.61; 'you.': 0.62; 'developed': 0.63; 'happen': 0.63; 'our': 0.64; 'more': 0.64; 'forward': 0.65; 'charset:windows-1252': 0.65; 'due': 0.66; 'smith': 0.68; 'bow': 0.84; 'comparable': 0.84; 'otten': 0.84; 'samsung': 0.84; 'dealt': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Mark Lawrence Subject: Re: Bug in timsort!? Date: Wed, 25 Feb 2015 16:55:12 +0000 References: <1cf84559-3a63-4799-a879-ae8e513d387e@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: host-92-24-216-15.ppp.as43234.net User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 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: 38 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1424883341 news.xs4all.nl 2849 [2001:888:2000:d::a6]:39394 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:86420 On 25/02/2015 16:04, Peter Otten wrote: > Sturla Molden wrote: > >> On 24/02/15 22:34, Roy Smith wrote: >>> http://envisage-project.eu/proving-android-java-and-python-sorting-algorithm-is-broken-and-how-to-fix-it/ >>> >> >> This is awful. It is broken for arrays longer than 2**49 elements. With >> 8 bytes per PyObject* pointer this is >4096 terabytes of RAM. I don't >> see how we can fix this in time. >> >> Oh yes, and they mention that TimSort is used on billions of devices due >> to Android mobile phones. This is clearly very relevant for mobile >> phones. Next thing you know your litte Samsung Galaxy with more than >> 4096 terabytes breaks down from a stack overflow in TimSort. > > Yeah, I'm looking forward to see comparable bugs being closed as "cannot > reproduce" by some of the jokers. I suppose that you all had a note > scribbled on the margin of your copy of Arithmetica that this cannot happen > with arrays of lengths seen in practice until 2038 or so. > > These guys found a bug that is subtler than what most of us have dealt with > in a widely used piece of code originally developed by one of the smarter > members of the python "community". > > I bow my head to them and say thank you. > Reading the bug report http://bugs.python.org/issue23515, specifically msg236586, it looks as if the proposed fix was wrong and one of the smarter members of the python community fixed it. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence