mirror of
https://github.com/python/cpython.git
synced 2025-07-24 11:44:31 +00:00
Consistency: "{\bf ...}" ==> "\strong{...}"
"{\em ...}" ==> "\emph{...}" Not at all sure what to do with "{\rm ...}". Leaving it for now.
This commit is contained in:
parent
b215137224
commit
af8a015c93
34 changed files with 62 additions and 60 deletions
|
@ -25,13 +25,13 @@ class instances):
|
|||
\begin{itemize}
|
||||
|
||||
\item
|
||||
A {\em shallow copy} constructs a new compound object and then (to the
|
||||
extent possible) inserts {\em references} into it to the objects found
|
||||
A \emph{shallow copy} constructs a new compound object and then (to the
|
||||
extent possible) inserts \emph{references} into it to the objects found
|
||||
in the original.
|
||||
|
||||
\item
|
||||
A {\em deep copy} constructs a new compound object and then,
|
||||
recursively, inserts {\em copies} into it of the objects found in the
|
||||
A \emph{deep copy} constructs a new compound object and then,
|
||||
recursively, inserts \emph{copies} into it of the objects found in the
|
||||
original.
|
||||
|
||||
\end{itemize}
|
||||
|
@ -46,7 +46,7 @@ Recursive objects (compound objects that, directly or indirectly,
|
|||
contain a reference to themselves) may cause a recursive loop.
|
||||
|
||||
\item
|
||||
Because deep copy copies {\em everything} it may copy too much, e.g.\
|
||||
Because deep copy copies \emph{everything} it may copy too much, e.g.\
|
||||
administrative data structures that should be shared even between
|
||||
copies.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue