Bug in slice type

[Michael Hudson]

bryanjugglercryptographer at yahoo.com writes:

> Michael Hudson wrote:
>> Bryan Olson writes:
>> In some sense; it certainly does what I intended it to do.
>
> [...]
>> I'm not going to change the behaviour.  The docs probably aren't
>> especially clear, though.
>
> The docs and the behavior contradict:
>
>     [...] these are the /start/ and /stop/ indices and the
>     /step/ or stride length of the slice [emphasis added].
>
>
> I'm fine with your favored behavior. What do we do next to get
> the doc fixed?

I guess one of us comes up with some less misleading words.  It's not
totally obvious to me what to do, seeing as the returned values *are*
indices is a sense, just not the sense in which they are used in
Python.  Any ideas?

Cheers,
mwh

-- 
  First of all, email me your AOL password as a security measure. You
  may find that won't be able to connect to the 'net for a while. This
  is normal. The next thing to do is turn your computer upside down
  and shake it to reboot it.                     -- Darren Tucker, asr