tuples, index method, Python's design

Chris Mellon arkanes at gmail.com
Wed Apr 11 16:14:02 CEST 2007


On 4/10/07, BJörn Lindqvist <bjourne at gmail.com> wrote:
> > > while not game_has_ended:
> > >   for current_player in p:
> > >     player_does_something(current_player)
> > >
> >
> > I'm curious why someone would even consider using a tuple in this case
> > regardless. I think that much of the desire for tuple.index is because
> > people use a tuple where they could have a list, but either a) some
> > vestige of B&D language programming comes out and they want to make
>
> Maybe someone had to much alcohol when they were coding? Maybe they
> don't know better? Maybe they thought that an index method on a
> sequence made sense? Who are you to spoil their fun? Could it be that
> YOU are the B&D person?
>

If you want a language that just adds whatever methods anyone thinks
of, along with whatever aliases for it any can think of, to every data
type, you know where to find Ruby.



More information about the Python-list mailing list