➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tshepang
Recipients Ramchandra Apte, docs@python, eric.araujo, ezio.melotti, ned.deily, terry.reedy, tim.golden, tshepang
Date 2012-02-26.00:02:09
SpamBayes Score 3.0665942e-05
Marked as misclassified No
Message-id <CAA77j2CpdqJCfp3aDPpEB5f6tZ6h5w1ktGamTkMQHJ8qcOK-Dw@mail.gmail.com>
In-reply-to <1330207884.28.0.757357127524.issue14112@psf.upfronthosting.co.za>
Content 
On Sun, Feb 26, 2012 at 00:11, Ned Deily <report@bugs.python.org> wrote:
> "shallow copy" and "deep copy" are both standard computer science terms by no means unique to or invented by Python.  We should be cautious about documentation bloat and trying to redefine standard terms.
>
> http://en.wikipedia.org/wiki/Object_copy#Shallow_copy

Do they mean exactly the same thing in Python as what Wikipedia says?
In that case, are links to Wikipedia allowed?

Anyways, some explanation (or link) would be needed since many people
without a background in computer science are going to read the
tutorial. I think the term is not common enough that it can be taken
for granted that newbies to Python (readers of the tutorial) will know
it.
History
Date User Action Args
2012-02-26 00:02:10tshepangsetrecipients: + tshepang, terry.reedy, tim.golden, ned.deily, ezio.melotti, eric.araujo, docs@python, Ramchandra Apte
2012-02-26 00:02:10tshepanglinkissue14112 messages
2012-02-26 00:02:09tshepangcreate