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 r.david.murray
Recipients Mariatta, docs@python, marco.buttu, ncoghlan, pgacv2, r.david.murray, serhiy.storchaka, steven.daprano, zach.ware
Date 2017-03-27.17:21:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490635275.44.0.393733970721.issue29506@psf.upfronthosting.co.za>
In-reply-to
Content
Looking over the PR, and especially in the context of Serhiy's point about this being about 'deep copy' and not 'deepcopy', I think this would be clearer if it were shortened even further, to just:

"Because deep copy copies everything, it may copy data that is intended to be shared between copies."

After all, what deepcopy does it provide a way for a class to implement that sharing when a deepcopy is done.
History
Date User Action Args
2017-03-27 17:21:15r.david.murraysetrecipients: + r.david.murray, ncoghlan, steven.daprano, docs@python, zach.ware, serhiy.storchaka, marco.buttu, Mariatta, pgacv2
2017-03-27 17:21:15r.david.murraysetmessageid: <1490635275.44.0.393733970721.issue29506@psf.upfronthosting.co.za>
2017-03-27 17:21:15r.david.murraylinkissue29506 messages
2017-03-27 17:21:15r.david.murraycreate