mirror of
https://github.com/python/cpython.git
synced 2025-08-02 08:02:56 +00:00
Fixed latex2html weirdness with footnotes.
This commit is contained in:
parent
45b0aeda3c
commit
ea003fcc2a
5 changed files with 42 additions and 43 deletions
|
@ -11,13 +11,13 @@ values in a binary format. The format is specific to Python, but
|
||||||
independent of machine architecture issues (e.g., you can write a
|
independent of machine architecture issues (e.g., you can write a
|
||||||
Python value to a file on a PC, transport the file to a Sun, and read
|
Python value to a file on a PC, transport the file to a Sun, and read
|
||||||
it back there). Details of the format are undocumented on purpose;
|
it back there). Details of the format are undocumented on purpose;
|
||||||
it may change between Python versions (although it rarely does).%
|
it may change between Python versions (although it rarely
|
||||||
\footnote{The name of this module stems from a bit of terminology used
|
does).\footnote{The name of this module stems from a bit of
|
||||||
by the designers of Modula-3 (amongst others), who use the term
|
terminology used by the designers of Modula-3 (amongst others), who
|
||||||
``marshalling'' for shipping of data around in a self-contained form.
|
use the term ``marshalling'' for shipping of data around in a
|
||||||
Strictly speaking, ``to marshal'' means to convert some data from
|
self-contained form. Strictly speaking, ``to marshal'' means to
|
||||||
internal to external form (in an RPC buffer for instance) and
|
convert some data from internal to external form (in an RPC buffer for
|
||||||
``unmarshalling'' for the reverse process.}
|
instance) and ``unmarshalling'' for the reverse process.}
|
||||||
|
|
||||||
This is not a general ``persistency'' module. For general persistency
|
This is not a general ``persistency'' module. For general persistency
|
||||||
and transfer of Python objects through RPC calls, see the modules
|
and transfer of Python objects through RPC calls, see the modules
|
||||||
|
@ -46,12 +46,12 @@ transfer plain Python integers, such values are silently truncated.
|
||||||
This particularly affects the use of very long integer literals in
|
This particularly affects the use of very long integer literals in
|
||||||
Python modules --- these will be accepted by the parser on such
|
Python modules --- these will be accepted by the parser on such
|
||||||
machines, but will be silently be truncated when the module is read
|
machines, but will be silently be truncated when the module is read
|
||||||
from the \file{.pyc} instead.%
|
from the \file{.pyc} instead.\footnote{
|
||||||
\footnote{A solution would be to refuse such literals in the parser,
|
A solution would be to refuse such literals in the parser,
|
||||||
since they are inherently non-portable. Another solution would be to
|
since they are inherently non-portable. Another solution would be to
|
||||||
let the \module{marshal} module raise an exception when an integer
|
let the \module{marshal} module raise an exception when an integer
|
||||||
value would be truncated. At least one of these solutions will be
|
value would be truncated. At least one of these solutions will be
|
||||||
implemented in a future version.}
|
implemented in a future version.}
|
||||||
|
|
||||||
There are functions that read/write files as well as functions
|
There are functions that read/write files as well as functions
|
||||||
operating on strings.
|
operating on strings.
|
||||||
|
|
|
@ -6,8 +6,8 @@ Names for built-in exceptions and functions are found in a separate
|
||||||
symbol table. This table is searched last when the interpreter looks
|
symbol table. This table is searched last when the interpreter looks
|
||||||
up the meaning of a name, so local and global
|
up the meaning of a name, so local and global
|
||||||
user-defined names can override built-in names. Built-in types are
|
user-defined names can override built-in names. Built-in types are
|
||||||
described together here for easy reference.%
|
described together here for easy reference.\footnote{
|
||||||
\footnote{Most descriptions sorely lack explanations of the exceptions
|
Most descriptions sorely lack explanations of the exceptions
|
||||||
that may be raised --- this will be fixed in a future version of
|
that may be raised --- this will be fixed in a future version of
|
||||||
this manual.}
|
this manual.}
|
||||||
\indexii{built-in}{types}
|
\indexii{built-in}{types}
|
||||||
|
|
|
@ -1,14 +1,13 @@
|
||||||
\chapter{The Python Profiler}
|
\chapter{The Python Profiler \label{profile}}
|
||||||
\label{profile}
|
|
||||||
|
\sectionauthor{James Roskind}{}
|
||||||
|
|
||||||
Copyright \copyright{} 1994, by InfoSeek Corporation, all rights reserved.
|
Copyright \copyright{} 1994, by InfoSeek Corporation, all rights reserved.
|
||||||
\index{InfoSeek Corporation}
|
\index{InfoSeek Corporation}
|
||||||
|
|
||||||
Written by James Roskind\index{Roskind, James}.%
|
Written by James Roskind.\footnote{
|
||||||
\footnote{
|
Updated and converted to \LaTeX\ by Guido van Rossum. The references to
|
||||||
Updated and converted to \LaTeX\ by Guido van Rossum. The references to
|
the old profiler are left in the text, although it no longer exists.}
|
||||||
the old profiler are left in the text, although it no longer exists.
|
|
||||||
}
|
|
||||||
|
|
||||||
Permission to use, copy, modify, and distribute this Python software
|
Permission to use, copy, modify, and distribute this Python software
|
||||||
and its associated documentation for any purpose (subject to the
|
and its associated documentation for any purpose (subject to the
|
||||||
|
@ -497,12 +496,11 @@ ordering are identical to the \method{print_callers()} method.
|
||||||
\end{methoddesc}
|
\end{methoddesc}
|
||||||
|
|
||||||
\begin{methoddesc}{ignore}{}
|
\begin{methoddesc}{ignore}{}
|
||||||
\deprecated{1.5.1}{This is not needed in modern versions of Python.%
|
\deprecated{1.5.1}{This is not needed in modern versions of
|
||||||
\footnote{
|
Python.\footnote{
|
||||||
This was once necessary, when Python would print any unused expression
|
This was once necessary, when Python would print any unused expression
|
||||||
result that was not \code{None}. The method is still defined for
|
result that was not \code{None}. The method is still defined for
|
||||||
backward compatibility.
|
backward compatibility.}}
|
||||||
}}
|
|
||||||
\end{methoddesc}
|
\end{methoddesc}
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -188,9 +188,9 @@ operator has operands of different numeric types, the operand with the
|
||||||
``smaller'' type is converted to that of the other, where plain
|
``smaller'' type is converted to that of the other, where plain
|
||||||
integer is smaller than long integer is smaller than floating point is
|
integer is smaller than long integer is smaller than floating point is
|
||||||
smaller than complex.
|
smaller than complex.
|
||||||
Comparisons between numbers of mixed type use the same rule.%
|
Comparisons between numbers of mixed type use the same rule.\footnote{
|
||||||
\footnote{As a consequence, the list \code{[1, 2]} is considered equal
|
As a consequence, the list \code{[1, 2]} is considered equal
|
||||||
to \code{[1.0, 2.0]}, and similar for tuples.}
|
to \code{[1.0, 2.0]}, and similar for tuples.}
|
||||||
The functions \function{int()}, \function{long()}, \function{float()},
|
The functions \function{int()}, \function{long()}, \function{float()},
|
||||||
and \function{complex()} can be used
|
and \function{complex()} can be used
|
||||||
to coerce numbers to a specific type.
|
to coerce numbers to a specific type.
|
||||||
|
@ -386,8 +386,8 @@ operation.
|
||||||
|
|
||||||
The right argument should be a tuple with one item for each argument
|
The right argument should be a tuple with one item for each argument
|
||||||
required by the format string; if the string requires a single
|
required by the format string; if the string requires a single
|
||||||
argument, the right argument may also be a single non-tuple object.%
|
argument, the right argument may also be a single non-tuple
|
||||||
\footnote{A tuple object in this case should be a singleton.}
|
object.\footnote{A tuple object in this case should be a singleton.}
|
||||||
The following format characters are understood:
|
The following format characters are understood:
|
||||||
\code{\%}, \code{c}, \code{s}, \code{i}, \code{d}, \code{u}, \code{o},
|
\code{\%}, \code{c}, \code{s}, \code{i}, \code{d}, \code{u}, \code{o},
|
||||||
\code{x}, \code{X}, \code{e}, \code{E}, \code{f}, \code{g}, \code{G}.
|
\code{x}, \code{X}, \code{e}, \code{E}, \code{f}, \code{g}, \code{G}.
|
||||||
|
@ -404,11 +404,11 @@ the string.
|
||||||
|
|
||||||
For safety reasons, floating point precisions are clipped to 50;
|
For safety reasons, floating point precisions are clipped to 50;
|
||||||
\code{\%f} conversions for numbers whose absolute value is over 1e25
|
\code{\%f} conversions for numbers whose absolute value is over 1e25
|
||||||
are replaced by \code{\%g} conversions.%
|
are replaced by \code{\%g} conversions.\footnote{
|
||||||
\footnote{These numbers are fairly arbitrary. They are intended to
|
These numbers are fairly arbitrary. They are intended to
|
||||||
avoid printing endless strings of meaningless digits without hampering
|
avoid printing endless strings of meaningless digits without hampering
|
||||||
correct use and without having to know the exact precision of floating
|
correct use and without having to know the exact precision of floating
|
||||||
point values on a particular machine.}
|
point values on a particular machine.}
|
||||||
All other errors raise exceptions.
|
All other errors raise exceptions.
|
||||||
|
|
||||||
If the right argument is a dictionary (or any kind of mapping), then
|
If the right argument is a dictionary (or any kind of mapping), then
|
||||||
|
@ -763,8 +763,8 @@ descriptors, e.g. module \module{fcntl} or \function{os.read()} and friends.
|
||||||
|
|
||||||
\begin{methoddesc}[file]{readline}{\optional{size}}
|
\begin{methoddesc}[file]{readline}{\optional{size}}
|
||||||
Read one entire line from the file. A trailing newline character is
|
Read one entire line from the file. A trailing newline character is
|
||||||
kept in the string%
|
kept in the string\footnote{
|
||||||
\footnote{The advantage of leaving the newline on is that an empty string
|
The advantage of leaving the newline on is that an empty string
|
||||||
can be returned to mean \EOF{} without being ambiguous. Another
|
can be returned to mean \EOF{} without being ambiguous. Another
|
||||||
advantage is that (in cases where it might matter, e.g. if you
|
advantage is that (in cases where it might matter, e.g. if you
|
||||||
want to make an exact copy of a file while scanning its lines)
|
want to make an exact copy of a file while scanning its lines)
|
||||||
|
|
|
@ -42,9 +42,10 @@ The following functions are defined in the \module{stdwin} module:
|
||||||
|
|
||||||
\begin{funcdesc}{open}{title}
|
\begin{funcdesc}{open}{title}
|
||||||
Open a new window whose initial title is given by the string argument.
|
Open a new window whose initial title is given by the string argument.
|
||||||
Return a window object; window object methods are described below.%
|
Return a window object; window object methods are described
|
||||||
\footnote{The Python version of STDWIN does not support draw procedures; all
|
below.\footnote{
|
||||||
drawing requests are reported as draw events.}
|
The Python version of STDWIN does not support draw procedures;
|
||||||
|
all drawing requests are reported as draw events.}
|
||||||
\end{funcdesc}
|
\end{funcdesc}
|
||||||
|
|
||||||
\begin{funcdesc}{getevent}{}
|
\begin{funcdesc}{getevent}{}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue