Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!newsfeed.eweka.nl!eweka.nl!feeder3.eweka.nl!newsfeed.xs4all.nl!newsfeed4.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.106 X-Spam-Level: * X-Spam-Evidence: '*H*': 0.80; '*S*': 0.01; 'happen,': 0.07; 'variable,': 0.07; 'python': 0.09; 'cest': 0.09; 'clock,': 0.09; 'loop.': 0.09; 'bug': 0.10; 'advance': 0.10; 'obviously,': 0.16; 'subject:)?': 0.16; 'mon,': 0.16; 'wrote:': 0.17; 'fix': 0.17; '>>>': 0.18; 'feb': 0.19; 'meant': 0.21; 'stephen': 0.22; 'seems': 0.23; 'specifically': 0.24; 'header:In-Reply-To:1': 0.25; 'header :User-Agent:1': 0.26; 'am,': 0.27; 'andrew': 0.27; 'accidentally': 0.29; 'adjust': 0.33; 'to:addr:python-list': 0.33; 'list': 0.35; 'along': 0.35; 'pm,': 0.35; 'really': 0.36; 'but': 0.36; 'should': 0.36; 'subject: (': 0.36; 'ok,': 0.37; 'subject:: ': 0.38; 'to:addr:python.org': 0.39; 'notice': 0.39; 'list,': 0.39; 'your': 0.60; 'easy': 0.60; 'received:phx3.secureserver.net': 0.62; 'received:prod.phx3.secureserver.net': 0.62; 'p.s.': 0.63; 'respect': 0.63; 'different': 0.63; 'effective': 0.63; 'helping': 0.63; 'more': 0.63; 'subject': 0.66; 'apologize': 0.67; 'header :Reply-To:1': 0.68; 'ranges': 0.71; 'reply-to:no real name:2**0': 0.72; '2013': 0.84; 'true!': 0.84; 'received:173.201': 0.91; 'received:173.201.192': 0.91; 'besides,': 0.93; 'forever.': 0.93; 'spoke': 0.93 Date: Mon, 25 Feb 2013 09:47:31 +0000 From: Andrew Robinson User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120909 Thunderbird/15.0.1 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Suggested feature: slice syntax within tuples (or even more generally)? References: <2e07acfb-4f48-4a27-9b06-3d8103325c0f@googlegroups.com> <512ABA02.2080709@r3dsolutions.com> <512B15C0.8070106@r3dsolutions.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: andrew3@r3dsolutions.com 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: 35 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1361814583 news.xs4all.nl 6963 [2001:888:2000:d::a6]:33793 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:39901 On 02/25/2013 04:54 PM, Ian Kelly wrote: > On Mon, Feb 25, 2013 at 12:41 AM, Andrew Robinson > wrote: >>> Intuitively, it should result in an infinite loop starting at 0. But >>> ranges require a stop value for a very good reason -- it should not be >>> this easy to accidentally create an infinite for loop. >> ... >> and, besides, the same is true with other constructions of loops.... >> >> while a: # Damn easy, if a is accidentally true! > Notice I specifically said an "infinite *for* loop". OK, so tit for tat. Notice I already showed an effective *accidental* "infinite" for loop because I did notice you spoke about a *for* loop. And, obviously, in the case of the while loop I showed -- it was not meant to be True forever. It's a variable, which is subject to change. I really do respect your opinion; but it's one of about 5 people that dominate this list, albeit the same spend a lot of time helping others; Stephen is someone new to me, and I want to encourage his probing of the issue more than I want to advance my view. P.S. I apologize about the e-mail clock, it seems I am sending my local time again -- and it's different from your timezone; I *wish* the python list computer would politely adjust it when *accidents* happen, or my OS's distribution would fix their bug -- but cest la vie. I limp along with the status quo for now.