summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Doc/lib/libbase64.tex2
-rw-r--r--Doc/lib/libfnmatch.tex2
-rw-r--r--Doc/lib/libquopri.tex2
-rw-r--r--Doc/lib/libsocksvr.tex2
-rw-r--r--Doc/libbase64.tex2
-rw-r--r--Doc/libfnmatch.tex2
-rw-r--r--Doc/libquopri.tex2
-rw-r--r--Doc/libsocksvr.tex2
8 files changed, 16 insertions, 0 deletions
diff --git a/Doc/lib/libbase64.tex b/Doc/lib/libbase64.tex
index ab00ded..edd1920 100644
--- a/Doc/lib/libbase64.tex
+++ b/Doc/lib/libbase64.tex
@@ -13,6 +13,8 @@ string \code{'www.python.org'} is encoded as the string
\indexii{RFC}{1421}
\index{MIME, base 64 encoding}
+\renewcommand{\indexsubitem}{(in module base64)}
+
\begin{funcdesc}{decode}{input\, output}
Decode the contents of the \var{input} file and write the resulting
binary data to the \var{output} file.
diff --git a/Doc/lib/libfnmatch.tex b/Doc/lib/libfnmatch.tex
index 86c9073..8bce50a 100644
--- a/Doc/lib/libfnmatch.tex
+++ b/Doc/lib/libfnmatch.tex
@@ -17,6 +17,8 @@ Note that the filename separator (\code{'/'} on Unix) is \emph{not}
special to this module. See module \code{glob} for pathname expansion
(\code{glob} uses \code{fnmatch} to match filename segments).
+\renewcommand{\indexsubitem}{(in module fnmatch)}
+
\begin{funcdesc}{fnmatch}{filename\, pattern}
Test whether the \var{filename} string matches the \var{pattern}
string, returning true or false. If the operating system is
diff --git a/Doc/lib/libquopri.tex b/Doc/lib/libquopri.tex
index 2fbd35a..a7395ec 100644
--- a/Doc/lib/libquopri.tex
+++ b/Doc/lib/libquopri.tex
@@ -12,6 +12,8 @@ are many such characters, as when sending a graphics file.
\indexii{RFC}{1521}
\index{MIME!quoted-printable encoding}
+\renewcommand{\indexsubitem}{(in module quopri)}
+
\begin{funcdesc}{decode}{input\, output}
Decode the contents of the \var{input} file and write the resulting
decoded binary data to the \var{output} file.
diff --git a/Doc/lib/libsocksvr.tex b/Doc/lib/libsocksvr.tex
index 1e3cac3..a45b948 100644
--- a/Doc/lib/libsocksvr.tex
+++ b/Doc/lib/libsocksvr.tex
@@ -36,6 +36,8 @@ many requests.
Server classes have the same external methods and attributes, no
matter what network protocol they use:
+\renewcommand{\indexsubitem}{(in module SocketServer)}
+
%XXX should data and methods be intermingled, or separate?
% how should the distinction between class and instance variables be
% drawn?
diff --git a/Doc/libbase64.tex b/Doc/libbase64.tex
index ab00ded..edd1920 100644
--- a/Doc/libbase64.tex
+++ b/Doc/libbase64.tex
@@ -13,6 +13,8 @@ string \code{'www.python.org'} is encoded as the string
\indexii{RFC}{1421}
\index{MIME, base 64 encoding}
+\renewcommand{\indexsubitem}{(in module base64)}
+
\begin{funcdesc}{decode}{input\, output}
Decode the contents of the \var{input} file and write the resulting
binary data to the \var{output} file.
diff --git a/Doc/libfnmatch.tex b/Doc/libfnmatch.tex
index 86c9073..8bce50a 100644
--- a/Doc/libfnmatch.tex
+++ b/Doc/libfnmatch.tex
@@ -17,6 +17,8 @@ Note that the filename separator (\code{'/'} on Unix) is \emph{not}
special to this module. See module \code{glob} for pathname expansion
(\code{glob} uses \code{fnmatch} to match filename segments).
+\renewcommand{\indexsubitem}{(in module fnmatch)}
+
\begin{funcdesc}{fnmatch}{filename\, pattern}
Test whether the \var{filename} string matches the \var{pattern}
string, returning true or false. If the operating system is
diff --git a/Doc/libquopri.tex b/Doc/libquopri.tex
index 2fbd35a..a7395ec 100644
--- a/Doc/libquopri.tex
+++ b/Doc/libquopri.tex
@@ -12,6 +12,8 @@ are many such characters, as when sending a graphics file.
\indexii{RFC}{1521}
\index{MIME!quoted-printable encoding}
+\renewcommand{\indexsubitem}{(in module quopri)}
+
\begin{funcdesc}{decode}{input\, output}
Decode the contents of the \var{input} file and write the resulting
decoded binary data to the \var{output} file.
diff --git a/Doc/libsocksvr.tex b/Doc/libsocksvr.tex
index 1e3cac3..a45b948 100644
--- a/Doc/libsocksvr.tex
+++ b/Doc/libsocksvr.tex
@@ -36,6 +36,8 @@ many requests.
Server classes have the same external methods and attributes, no
matter what network protocol they use:
+\renewcommand{\indexsubitem}{(in module SocketServer)}
+
%XXX should data and methods be intermingled, or separate?
% how should the distinction between class and instance variables be
% drawn?