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 Julian, brett.cannon, chris.jerdonek, daniel.urban, eric.araujo, ezio.melotti, michael.foord, pablomouzo, r.david.murray
Date 2012-09-19.00:33:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348014792.26.0.817044157633.issue11664@psf.upfronthosting.co.za>
In-reply-to
Content
I actually agree with Julian here.  I much prefer patch.object and do my best to avoid mock.patch.  support.patch is also equivalent to patch.object and not patch.  That doesn't change the fact that other people prefer mock.patch, of course.

I think mock.patch is too "magical" for my taste.  There is something I don't like about the dynamic import, even though I can't really tell you what it is :)
History
Date User Action Args
2012-09-19 00:33:12r.david.murraysetrecipients: + r.david.murray, brett.cannon, ezio.melotti, eric.araujo, michael.foord, pablomouzo, daniel.urban, chris.jerdonek, Julian
2012-09-19 00:33:12r.david.murraysetmessageid: <1348014792.26.0.817044157633.issue11664@psf.upfronthosting.co.za>
2012-09-19 00:33:11r.david.murraylinkissue11664 messages
2012-09-19 00:33:11r.david.murraycreate