summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRaymond Hettinger <python@rcn.com>2003-09-12 00:02:37 (GMT)
committerRaymond Hettinger <python@rcn.com>2003-09-12 00:02:37 (GMT)
commit74c8e55f3b64b8819a1950be4ac1323c74931cc2 (patch)
treee670c94def0ad9ea4a65c864b2929873a79e01b2
parent614438ab069a222f2f2ac0927c786398314df2d5 (diff)
downloadcpython-74c8e55f3b64b8819a1950be4ac1323c74931cc2.zip
cpython-74c8e55f3b64b8819a1950be4ac1323c74931cc2.tar.gz
cpython-74c8e55f3b64b8819a1950be4ac1323c74931cc2.tar.bz2
SF bug #804280: fromkeys is not listed in index
-rw-r--r--Doc/lib/libstdtypes.tex9
1 files changed, 5 insertions, 4 deletions
diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex
index 6fb1180..c3a0305 100644
--- a/Doc/lib/libstdtypes.tex
+++ b/Doc/lib/libstdtypes.tex
@@ -1082,7 +1082,7 @@ almost arbitrary values. Only values containing lists, dictionaries
or other mutable types (that are compared by value rather than by
object identity) may not be used as keys.
Numeric types used for keys obey the normal rules for numeric
-comparison: if two numbers compare equal (e.g. \code{1} and
+comparison: if two numbers compare equal (such as \code{1} and
\code{1.0}) then they can be used interchangeably to index the same
dictionary entry.
@@ -1102,6 +1102,7 @@ arbitrary objects):
\ttindex{clear()}
\ttindex{copy()}
\ttindex{has_key()}
+ \ttindex{fromkeys()}
\ttindex{items()}
\ttindex{keys()}
\ttindex{update()}
@@ -1268,7 +1269,7 @@ Files have the following methods:
\end{methoddesc}
\begin{methoddesc}[file]{next}{}
-A file object is its own iterator, i.e. \code{iter(\var{f})} returns
+A file object is its own iterator, for example \code{iter(\var{f})} returns
\var{f} (unless \var{f} is closed). When a file is used as an
iterator, typically in a \keyword{for} loop (for example,
\code{for line in f: print line}), the \method{next()} method is
@@ -1506,8 +1507,8 @@ same as \code{\var{m}.__dict__} where \var{m} is the module in which
the function \var{f} was defined).
Function objects also support getting and setting arbitrary
-attributes, which can be used to, e.g. attach metadata to functions.
-Regular attribute dot-notation is used to get and set such
+attributes, which can be used, for example, to attach metadata to
+functions. Regular attribute dot-notation is used to get and set such
attributes. \emph{Note that the current implementation only supports
function attributes on user-defined functions. Function attributes on
built-in functions may be supported in the future.}