Always mark variables in the "Notes" following a table the same way as in the

tables:  \var{}

Add a couple of index entries to the File Objects section.
This commit is contained in:
Fred Drake 1998-01-20 05:20:39 +00:00
parent cbe50f4829
commit 73a973bf8d
2 changed files with 6 additions and 2 deletions

View File

@ -545,7 +545,7 @@ Notes:
\item[(2)] Keys and values are listed in random order.
\item[(3)] \code{b} must be of the same type as \code{a}.
\item[(3)] \var{b} must be of the same type as \var{a}.
\item[(4)] Never raises an exception if \var{k} is not in the map,
instead it returns \var{f}. \var{f} is optional, when not provided
@ -666,6 +666,8 @@ built-in functions and methods, e.g.\ \code{posix.popen()} and
\code{posix.fdopen()} and the \code{makefile()} method of socket
objects.
\bifuncindex{open}
\refbimodindex{posix}
\refbimodindex{socket}
When a file operation fails for an I/O-related reason, the exception
\code{IOError} is raised. This includes situations where the

View File

@ -545,7 +545,7 @@ Notes:
\item[(2)] Keys and values are listed in random order.
\item[(3)] \code{b} must be of the same type as \code{a}.
\item[(3)] \var{b} must be of the same type as \var{a}.
\item[(4)] Never raises an exception if \var{k} is not in the map,
instead it returns \var{f}. \var{f} is optional, when not provided
@ -666,6 +666,8 @@ built-in functions and methods, e.g.\ \code{posix.popen()} and
\code{posix.fdopen()} and the \code{makefile()} method of socket
objects.
\bifuncindex{open}
\refbimodindex{posix}
\refbimodindex{socket}
When a file operation fails for an I/O-related reason, the exception
\code{IOError} is raised. This includes situations where the