summaryrefslogtreecommitdiffstats
path: root/Doc/ref
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2000-07-13 04:57:58 (GMT)
committerFred Drake <fdrake@acm.org>2000-07-13 04:57:58 (GMT)
commit91826ed2a9e6f2b6f6b01f77b6d63532bf66d6f7 (patch)
treea5d96bc39d3b19d1fb70fa5cbf9b58a0dfe15d99 /Doc/ref
parent8d2f2b2db21bddfad17a0a52b4fdded558adf7fb (diff)
downloadcpython-91826ed2a9e6f2b6f6b01f77b6d63532bf66d6f7.zip
cpython-91826ed2a9e6f2b6f6b01f77b6d63532bf66d6f7.tar.gz
cpython-91826ed2a9e6f2b6f6b01f77b6d63532bf66d6f7.tar.bz2
Improve the descriptions of expected exceptions for __getitem__(),
__setitem__(), and __delitem__(). Based on related comments from Barry Warsaw.
Diffstat (limited to 'Doc/ref')
-rw-r--r--Doc/ref/ref3.tex18
1 files changed, 14 insertions, 4 deletions
diff --git a/Doc/ref/ref3.tex b/Doc/ref/ref3.tex
index 59b98de..4895c9b 100644
--- a/Doc/ref/ref3.tex
+++ b/Doc/ref/ref3.tex
@@ -1091,9 +1091,16 @@ returns zero is considered to be false in a Boolean context.
\begin{methoddesc}[mapping object]{__getitem__}{self, key}
Called to implement evaluation of \code{\var{self}[\var{key}]}.
-For a sequence types, the accepted keys should be integers. Note that the
-special interpretation of negative indices (if the class wishes to
+For a sequence types, the accepted keys should be integers. Note that
+the special interpretation of negative indices (if the class wishes to
emulate a sequence type) is up to the \method{__getitem__()} method.
+If \var{key} is of an inappropriate type, \exception{TypeError} may be
+raised; if of a value outside the set of indexes for the sequence
+(after any special interpretation of negative values),
+\exception{IndexError} should be raised.
+\strong{Note:} \keyword{for} loops expect that an
+\exception{IndexError} will be raised for illegal indexes to allow
+proper detection of the end of the sequence.
\end{methoddesc}
\begin{methoddesc}[mapping object]{__setitem__}{self, key, value}
@@ -1101,14 +1108,17 @@ Called to implement assignment to \code{\var{self}[\var{key}]}. Same
note as for \method{__getitem__()}. This should only be implemented
for mappings if the objects support changes to the values for keys, or
if new keys can be added, or for sequences if elements can be
-replaced.
+replaced. The same exceptions should be raised for improper
+\var{key} values as for the \method{__getitem__()} method.
\end{methoddesc}
\begin{methoddesc}[mapping object]{__delitem__}{self, key}
Called to implement deletion of \code{\var{self}[\var{key}]}. Same
note as for \method{__getitem__()}. This should only be implemented
for mappings if the objects support removal of keys, or for sequences
-if elements can be removed from the sequence.
+if elements can be removed from the sequence. The same exceptions
+should be raised for improper \var{key} values as for the
+\method{__getitem__()} method.
\end{methoddesc}