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 Julian, brett.cannon, chris.jerdonek, daniel.urban, eric.araujo, ezio.melotti, michael.foord, pablomouzo, r.david.murray
Date 2012-09-19.09:32:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348047126.6.0.854690363841.issue11664@psf.upfronthosting.co.za>
In-reply-to
Content
It maybe that patch.object is a more natural interface to the small sample of people commenting here, in which case great - that's what it's there for. 

However in common usage patch is used around two orders of magnitude more. I've seen large codebases with hundreds of uses of patch and only a handful of uses of patch.object.

To support the *minor* use case and not the major use case in TestCase would be an inanity.
History
Date User Action Args
2012-09-19 09:32:06michael.foordsetrecipients: + michael.foord, brett.cannon, ezio.melotti, eric.araujo, r.david.murray, pablomouzo, daniel.urban, chris.jerdonek, Julian
2012-09-19 09:32:06michael.foordsetmessageid: <1348047126.6.0.854690363841.issue11664@psf.upfronthosting.co.za>
2012-09-19 09:32:06michael.foordlinkissue11664 messages
2012-09-19 09:32:05michael.foordcreate