Scott Dial wrote: > Benjamin Peterson wrote: > >> Consider this error: >> >>>>> 3["something"] >>>>> >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> TypeError: 'int' object is unsubscriptable >> >> "unscriptable" seems rather ambiguous. How about "[object] cannot be indexed"? >> >> > > Although I think this is a bit of bike-shedding, I would point out that > CPython is itself inconsistent about this: > > >>> set([1,2,3])[0] > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: 'set' object is unindexable > > I tend to agree with Benjamin that "unsubscriptable" is a made-up word, > but so is "unindexable". So, whatever. > It seems to be more common in the 'Python world' to refer to indexing than subscription and I admit that this error message has confused me in the past. Michael > -Scott > >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4