Author ezio.melotti
Recipients docs@python, eric.araujo, ezio.melotti, terry.reedy, tshepang
Date 2012-02-25.08:09:40
SpamBayes Score 1.58282e-07
Marked as misclassified No
Message-id <1330157380.77.0.852681869193.issue14112@psf.upfronthosting.co.za>
In-reply-to
Content
Even if they know the meaning of "shallow" (which is not a really common word AFAICT), they might not know what it means in this context.

Adding an entry to glossary might be a better solution.

In this context I think the best solution would be to actually show the implication of having a shallow copy with another short example (hijacking the reader to some other page where they can find some in-depth description of what "shallow" might do more harm than good).
History
Date User Action Args
2012-02-25 08:09:40ezio.melottisetrecipients: + ezio.melotti, terry.reedy, eric.araujo, docs@python, tshepang
2012-02-25 08:09:40ezio.melottisetmessageid: <1330157380.77.0.852681869193.issue14112@psf.upfronthosting.co.za>
2012-02-25 08:09:40ezio.melottilinkissue14112 messages
2012-02-25 08:09:40ezio.melotticreate