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 Guillaume Chorn
Recipients Guillaume Chorn, michael.foord, r.david.murray, rbcollins
Date 2016-10-03.18:17:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1475518659.41.0.343405848976.issue28318@psf.upfronthosting.co.za>
In-reply-to
Content
If it's true that our ability to accurately deep-copy mutable args makes fixing this behavior impossible, we should at the very least update the official unittest.mock documentation to warn users that testing for mock calls with mutable arguments is not reliable; i.e. make it clear that we're storing a reference to the arguments and not just the values. If it's not a bug, it's certainly a limitation that deserves as much mention as possible.
History
Date User Action Args
2016-10-03 18:17:39Guillaume Chornsetrecipients: + Guillaume Chorn, rbcollins, r.david.murray, michael.foord
2016-10-03 18:17:39Guillaume Chornsetmessageid: <1475518659.41.0.343405848976.issue28318@psf.upfronthosting.co.za>
2016-10-03 18:17:39Guillaume Chornlinkissue28318 messages
2016-10-03 18:17:39Guillaume Chorncreate