Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #39901

Re: Suggested feature: slice syntax within tuples (or even more generally)?

Date 2013-02-25 09:47 +0000
From Andrew Robinson <andrew3@r3dsolutions.com>
Subject Re: Suggested feature: slice syntax within tuples (or even more generally)?
References (1 earlier) <kfhsc2$ubq$1@ger.gmane.org> <512ABA02.2080709@r3dsolutions.com> <CALwzid=Dobx0F1Gm3E-Oq0vZf8V6SaNmb3j4SBmty1DDAffwLg@mail.gmail.com> <512B15C0.8070106@r3dsolutions.com> <CALwzid=SscH6kcPXFGZL5Oh=rQDm=1yxZ6=mibdYssgHCGxcuw@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.2513.1361814583.2939.python-list@python.org> (permalink)

Show all headers | View raw


On 02/25/2013 04:54 PM, Ian Kelly wrote:
> On Mon, Feb 25, 2013 at 12:41 AM, Andrew Robinson
> <andrew3@r3dsolutions.com> 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.



Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-13 11:00 -0800
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Terry Reedy <tjreedy@udel.edu> - 2013-02-14 00:23 -0500
    Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-13 21:54 -0800
    Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-13 21:54 -0800
      Re: Suggested feature: slice syntax within tuples (or even more generally)? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-02-14 07:32 +0000
        Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 00:36 -0800
      Re: Suggested feature: slice syntax within tuples (or even more generally)? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-02-14 08:03 +0000
        Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 01:08 -0800
          Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 01:26 -0800
        Re: Suggested feature: slice syntax within tuples (or even more generally)? Ian Kelly <ian.g.kelly@gmail.com> - 2013-02-14 11:58 -0700
          Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 14:01 -0800
          Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 14:01 -0800
            Re: Suggested feature: slice syntax within tuples (or even more generally)? Rick Johnson <rantingrickjohnson@gmail.com> - 2013-02-14 17:46 -0800
            Re: Suggested feature: slice syntax within tuples (or even more generally)? Rick Johnson <rantingrickjohnson@gmail.com> - 2013-02-14 17:46 -0800
  Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-13 22:06 -0800
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Duncan Booth <duncan.booth@invalid.invalid> - 2013-02-14 12:25 +0000
    Re: Suggested feature: slice syntax within tuples (or even more generally)? stephenwlin@gmail.com - 2013-02-14 07:56 -0800
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Andrew Robinson <andrew3@r3dsolutions.com> - 2013-02-25 01:10 +0000
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Ian Kelly <ian.g.kelly@gmail.com> - 2013-02-25 03:28 -0700
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Terry Reedy <tjreedy@udel.edu> - 2013-02-25 06:23 -0500
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Ian Kelly <ian.g.kelly@gmail.com> - 2013-02-25 09:54 -0700
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Andrew Robinson <andrew3@r3dsolutions.com> - 2013-02-25 09:47 +0000
  Re: Suggested feature: slice syntax within tuples (or even more generally)? Nobody <nobody@nowhere.com> - 2013-02-26 07:38 +0000

csiph-web