➜

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 josh.r
Recipients introom, josh.r, nadeem.vawda, serhiy.storchaka, twouters
Date 2016-01-20.18:12:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453313576.05.0.930183367959.issue25007@psf.upfronthosting.co.za>
In-reply-to
Content 
Patch looks good, but incomplete. Supporting __deepcopy__ (as a simple wrapper around __copy__ that ignores the second argument) would provide complete support.

Also, should there be tests? I mean, I assume the .copy() method itself is tested, but just to detect stupid regressions, seems like testing __copy__/__deepcopy__ for identical behavior would be a good thing.
History
Date User Action Args
2016-01-20 18:12:56josh.rsetrecipients: + josh.r, twouters, nadeem.vawda, serhiy.storchaka, introom
2016-01-20 18:12:56josh.rsetmessageid: <1453313576.05.0.930183367959.issue25007@psf.upfronthosting.co.za>
2016-01-20 18:12:56josh.rlinkissue25007 messages
2016-01-20 18:12:56josh.rcreate