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 rbcollins
Recipients berker.peksag, michael.foord, pkoning, python-dev, quasipedia, rbcollins
Date 2015-07-22.04:23:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437538987.29.0.0740463250067.issue21750@psf.upfronthosting.co.za>
In-reply-to
Content
So the 1.1.4 behaviour matches that of a VFS most closely. But, see the earlier messages, it does do only and precisely because it breaks regular mock idioms. Thus I think we're better off with the new patch, which addresses the issue with reuse of the mocks in subclassed tests(with the patch decorator), as well as with repeated opens, while still preserving the basic structure and feel of 'Mock'.
History
Date User Action Args
2015-07-22 04:23:07rbcollinssetrecipients: + rbcollins, michael.foord, python-dev, quasipedia, berker.peksag, pkoning
2015-07-22 04:23:07rbcollinssetmessageid: <1437538987.29.0.0740463250067.issue21750@psf.upfronthosting.co.za>
2015-07-22 04:23:07rbcollinslinkissue21750 messages
2015-07-22 04:23:07rbcollinscreate