mirror of
https://github.com/python/cpython.git
synced 2025-07-24 03:35:53 +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
|
||||
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 may change between Python versions (although it rarely does).%
|
||||
\footnote{The name of this module stems from a bit of terminology used
|
||||
by the designers of Modula-3 (amongst others), who use the term
|
||||
``marshalling'' for shipping of data around in a self-contained form.
|
||||
Strictly speaking, ``to marshal'' means to convert some data from
|
||||
internal to external form (in an RPC buffer for instance) and
|
||||
``unmarshalling'' for the reverse process.}
|
||||
it may change between Python versions (although it rarely
|
||||
does).\footnote{The name of this module stems from a bit of
|
||||
terminology used by the designers of Modula-3 (amongst others), who
|
||||
use the term ``marshalling'' for shipping of data around in a
|
||||
self-contained form. Strictly speaking, ``to marshal'' means to
|
||||
convert some data from internal to external form (in an RPC buffer for
|
||||
instance) and ``unmarshalling'' for the reverse process.}
|
||||
|
||||
This is not a general ``persistency'' module. For general persistency
|
||||
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
|
||||
Python modules --- these will be accepted by the parser on such
|
||||
machines, but will be silently be truncated when the module is read
|
||||
from the \file{.pyc} instead.%
|
||||
\footnote{A solution would be to refuse such literals in the parser,
|
||||
since they are inherently non-portable. Another solution would be to
|
||||
let the \module{marshal} module raise an exception when an integer
|
||||
value would be truncated. At least one of these solutions will be
|
||||
implemented in a future version.}
|
||||
from the \file{.pyc} instead.\footnote{
|
||||
A solution would be to refuse such literals in the parser,
|
||||
since they are inherently non-portable. Another solution would be to
|
||||
let the \module{marshal} module raise an exception when an integer
|
||||
value would be truncated. At least one of these solutions will be
|
||||
implemented in a future version.}
|
||||
|
||||
There are functions that read/write files as well as functions
|
||||
operating on strings.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue