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 michael.foord
Recipients michael.foord
Date 2013-08-02.08:59:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375433959.37.0.622075627105.issue18622@psf.upfronthosting.co.za>
In-reply-to
Content
The best way to solve this seems to be to track a set of visited ids (mocks we've reset) and not recurse into mocks we've already done. This is similar to the patch proposed on the google code issue - but not identical as that uses a list and has it as the default argument to reset_mock.
History
Date User Action Args
2013-08-02 08:59:19michael.foordsetrecipients: + michael.foord
2013-08-02 08:59:19michael.foordsetmessageid: <1375433959.37.0.622075627105.issue18622@psf.upfronthosting.co.za>
2013-08-02 08:59:19michael.foordlinkissue18622 messages
2013-08-02 08:59:18michael.foordcreate