summaryrefslogtreecommitdiffstats
path: root/Doc/lib
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-01-19 04:02:41 (GMT)
committerFred Drake <fdrake@acm.org>1998-01-19 04:02:41 (GMT)
commit8095ebfc4a4ca613e294db8e512908c7a54e4ac9 (patch)
treeae663df7357e81b317184a93d907997a010a1950 /Doc/lib
parent63566e2ef22f48be9975c9994bc7889e6526264a (diff)
downloadcpython-8095ebfc4a4ca613e294db8e512908c7a54e4ac9.zip
cpython-8095ebfc4a4ca613e294db8e512908c7a54e4ac9.tar.gz
cpython-8095ebfc4a4ca613e294db8e512908c7a54e4ac9.tar.bz2
Consistency: Replaced 4 {\it ...} with \emph{...}.
Diffstat (limited to 'Doc/lib')
-rw-r--r--Doc/lib/libmpz.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libmpz.tex b/Doc/lib/libmpz.tex
index 2771d92..7ab5fe7 100644
--- a/Doc/lib/libmpz.tex
+++ b/Doc/lib/libmpz.tex
@@ -16,8 +16,8 @@ In general, \dfn{mpz}-numbers can be used just like other standard
Python numbers, e.g.\ you can use the built-in operators like \code{+},
\code{*}, etc., as well as the standard built-in functions like
\code{abs}, \code{int}, \ldots, \code{divmod}, \code{pow}.
-\strong{Please note:} the {\it bitwise-xor} operation has been implemented as
-a bunch of {\it and}s, {\it invert}s and {\it or}s, because the library
+\strong{Please note:} the \emph{bitwise-xor} operation has been implemented as
+a bunch of \emph{and}s, \emph{invert}s and \emph{or}s, because the library
lacks an \code{mpz_xor} function, and I didn't need one.
You create an mpz-number by calling the function called \code{mpz} (see