Tutorial creates confusion about slices

[Tim Golden]

Antoon Pardon wrote:
> On 2007-04-24, Michael Hoffman <cam.ac.uk at mh391.invalid> wrote:
> 
>> Really only one person has argued that the docs do not need to be 
>> changed. The other two people seemed to think you were asking for help 
>> rather than discussing how to revise the docs. Understandable, since 
>> that's why most people come to this group in my estimation.
>>
>> Your time is your own and it is good to spend your efforts on what you 
>> think will be most fruitful. But if you are going to let the opposition 
>> of one person stop you from doing anything, you will not accomplish very 
>> much.
> 
> sjdevnull at yahoo.com has brought a point that is worth considering.
> So I retreat now a bit to see if I can come with a proposal that
> bears in mind his point.

Now that this thread has slowed a little I would also
point out -- while agreeing with sjdevnull's thoughtful
post -- that reaction to an idea on a mailing list is
possibly not the best means of gauging its validity.
That's not to say you shouldn't listen to other posters;
rather that, if you still feel after due consideration
of other people's points of view that what you're
proposing is right, then go ahead and create a patch.

The people who are going to accept or reject your
doc patch are (probably) not the people who are
putting forward their ideas here on this list.
Ultimately, patches aren't voted in by the denizens
of python-list / c.l.py.

Also, there may be 1000 people nodding thoughtfully
(and silently) in agreement with your point of view, but
who are unlikely to post a "me, too" comment. It seems
likely that any posters are more likely to be those in
disagreement with a point of view.

Frankly, if you think after consideration that a change
to the docs is advisable, post up a patch to the relevant
place. If there are people on this list who disagree,
they're at liberty to comment on the patch. But at that
point, you've made the effort and said your piece. It's
up to the naysayers to make the effort to comment on
the patch. And, ultimately, up to the Python development
community to accept or reject it as they see fit. (And
as they have the time and inclination :)

TJG