➜

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 xtreak
Recipients Amir, Darragh Bailey, anthonypjshaw, aviso, cjw296, lisroach, mariocj89, michael.foord, pconnell, r.david.murray, rbcollins, xtreak
Date 2020-03-27.11:43:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585309435.37.0.0933351696984.issue39966@roundup.psfhosted.org>
In-reply-to
Content 
On thinking more about this the wraps argument provides a way to wrap the calls for the mock to a given object. So when an attribute not present in the wrapped object is being accessed then it should act like the attribute is not present. Falling back to the default value like previous case would help but that will pose the question over whether the value is from the wrapped object's attribute or from the default value for the magic method that the user could never know. This could be better clarified in the docs I suppose which I missed in the previous issue. 

Thoughts on this fallback behavior?
History
Date User Action Args
2020-03-27 11:43:55xtreaksetrecipients: + xtreak, rbcollins, cjw296, r.david.murray, michael.foord, pconnell, Darragh Bailey, lisroach, anthonypjshaw, mariocj89, aviso, Amir
2020-03-27 11:43:55xtreaksetmessageid: <1585309435.37.0.0933351696984.issue39966@roundup.psfhosted.org>
2020-03-27 11:43:55xtreaklinkissue39966 messages
2020-03-27 11:43:55xtreakcreate