Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: chris@rebertia.com
In-Reply-To: <cd108b9d-e951-463e-8e50-a5a024a27c7f@googlegroups.com>
References: <6998a955-7b34-4f4f-b8d6-62d1028f7561@googlegroups.com> <mailman.2986.1351482209.27098.python-list@python.org> <4c024364-84df-403b-8b9e-4a4c8f06121c@googlegroups.com> <mailman.2991.1351484760.27098.python-list@python.org> <cd108b9d-e951-463e-8e50-a5a024a27c7f@googlegroups.com>
Date: Mon, 29 Oct 2012 01:18:32 -0700
Subject: Re: Negative array indicies and slice()
From: Chris Rebert <clp2@rebertia.com>
To: Andrew <andrewr3mail@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Python <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2997.1351498716.27098.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:32348

On Mon, Oct 29, 2012 at 12:54 AM, Andrew <andrewr3mail@gmail.com> wrote:
> On Sunday, October 28, 2012 9:26:01 PM UTC-7, Ian wrote:
>> On Sun, Oct 28, 2012 at 10:00 PM,  Andrew wrote:
<snip>
> The slice class when passed to __getitem__()  was created to merely pass =
two numbers and a stride to __getitem__;  As far as I know slice() itself d=
oes *nothing* in the actual processing of the elements.  So, it's *redundan=
t* functionality, and far worse, it's restrictive.
>
> The philosophy of Python is to have exactly one way to do something when =
possible; so, why create a stand alone class that does nothing an existing =
class could already do, and do it better ?
>
> A simple list of three values would be just as efficient as slice()!
> xrange is more flexible, and can be just as efficient.
>
> So, Have I misunderstood the operation of slice()?  I think I might have.=
.. but I don't know.

`slice` is intentionally lenient about the types of the start, stop, and st=
ep:
>>> class Foo:
...     def __getitem__(self, slice_):
...         print(slice_)
...         return 42
...
>>> Foo()["a":"b":"c"]
slice('a', 'b', 'c')
42
>>>
Thus, the thing being sliced is free to interpret the parts of the
slice however it wishes; hence, slice() is unable to contain the
"processing" you speak of.
By contrast, xrange() limits itself to integers.
To support the more general case, the slice syntax thus produces a
`slice` rather than an `xrange`.
Doubtlessly, there are also historical issues involved. As implied by
the ugliness of its name, `xrange` was added to the language
relatively later.

Cheers,
Chris