tuples, index method, Python's design

Antoon Pardon apardon at forel.vub.ac.be
Tue Apr 10 03:45:05 EDT 2007


On 2007-04-08, Carsten Haese <carsten at uniqsys.com> wrote:
> On Sun, 2007-04-08 at 07:51 -0700, Paul Rubin wrote:
>> Carsten Haese <carsten at uniqsys.com> writes:
>> > > Maybe we can add such methods to the PyPy tuples for some time, to
>> > > experimentally see if they make the language worse :-)
>> > 
>> > Adding useless features always makes a product worse. What's your use
>> > case for tuple.index?
>> 
>> 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.

I don't agree. Good or bad design is not dependant on what is
implemented and what is not.

> 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.

You mean that those who are against tuple.index won't find any use case
convincing enough.

-- 
Antoon Pardon



More information about the Python-list mailing list