Python Question
Why is __getitem__ called in Python 3.5 but not in Python 2.7?
I have a subclass of bytes that provides a
__getitem____getitem____getitem__Code
class A(object):
def __getitem__(self, key):
print("in A.__getitem__ with key " + str(key))
return []
class B(bytes):
def __getitem__(self, key):
print("in B.__getitem__ with key " + str(key))
return []
if __name__ == "__main__":
import sys
print(sys.version)
a = A()
b = B()
print("[0]")
a[0]
b[0]
print("[0:1]")
a[0:1]
b[0:1]
print("[:1]")
a[:1]
b[:1]
Python 3.5 Output
The class-defined
__getitem__(venv) snafu$ python ./x.py
3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609]
[0]
in A.__getitem__ with key 0
in B.__getitem__ with key 0
[0:1]
in A.__getitem__ with key slice(0, 1, None)
in B.__getitem__ with key slice(0, 1, None)
[:1]
in A.__getitem__ with key slice(None, 1, None)
in B.__getitem__ with key slice(None, 1, None)
Python 2.7 Output
The class-defined
__getitem__(venv2.7) snafu$ python x.py
2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609]
[0]
in A.__getitem__ with key 0
in B.__getitem__ with key 0
[0:1]
in A.__getitem__ with key slice(0, 1, None)
[:1]
in A.__getitem__ with key slice(None, 1, None)
Recommended for you: Get network issues from WhatsUp Gold. Not end users.
Answer Source
Python 2 has __getslice__, which takes priority over __getitem__ for stepless slicing if present. That's gone in Python 3.
Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download