The __getitem__ of a tuple does not support the
extended slicing. That makes it difficult to delegate
from an object's __getitem__ to a builtin container,
which ought to work through delegating __getitem__

<pre>
class GI:
    def __getitem__(self,a):
        print a

a = GI()
a[1:2]
(1,2,3,4).__getitem__(slice(1,2,None))
</pre>

gives

slice(1, 2, None)
Traceback (most recent call last):
  File "bar.py", line 7, in ?
    (1,2,3,4).__getitem__(slice(1,2,None))

Logged In: YES 
user_id=6380

This is not just the __getitem__ -- t[...] also has this
problem.
As a workaround, you can define __getslice__ or parse the
slice() object yourself.

I'll eventually get around to fixing this, but it's a bit
messy.

Logged In: YES 
user_id=6380

See (revived) patch 400998?

Logged In: YES 
user_id=6380

MWH's patch has fixed this now.

Logged In: YES 
user_id=6656

Um, are you sure?

I still get

>>> (1,2,3).__getitem__(slice(1,2,3))
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
TypeError: an integer is required
[19426 refs]

Though:

>>> (1,2,3)[slice(1,2,3)]
(2,)
[19429 refs]

which is an improvement.

I guess this is for the same reason as #473985 is still open.

Logged In: YES 
user_id=6380

OK, this is now *really* fixed.