tuples, index method, Python's design

Carsten Haese carsten at uniqsys.com
Mon Apr 9 02:10:21 CEST 2007

On Sun, 2007-04-08 at 13:10 -0700, Paul Rubin wrote:
> Carsten Haese <carsten at uniqsys.com> writes:
> > > Do you not see the gratuituous inconsistency between tuples and lists
> > > as a useless feature?  What is the use case for keeping it?
> > 
> > When a new feature is requested, the burden of proof is on the requester
> > to show that it has uses. The use case for not having tuple.index is
> > that there are no use cases for having it. If that answer sounds absurd,
> > it is because your question is absurd.
> The use case has already been discussed.  Removing the pointless
> inconsistency between lists and tuples means you can stop having to
> remember it, so you can free up brain cells for implementing useful
> things.  That increases your programming productivity.

Will tuples also get a sort method? What about append and extend? pop?
__iadd__? __delslice__?

How many brain cells are actually freed up by not having to remember
that *one* method that you'd never use doesn't exist?


More information about the Python-list mailing list