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 berker.peksag, bignose, brett.cannon, carljm, erik.bray, fov, kevinbenton, kushal.das, michael.foord, poke, rbcollins, ztane
Date 2015-07-28.12:10:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I had a chance to talk to Guido about this at EuroPython. His feeling was that a separate set of functions *is* a better API - or at least would have been if mock had been designed this way from the start. 

However, the most serious problem with the current API is solved (as assert* attributes that don't exist now raise an AttributeError) and it isn't worth breaking people's code by deprecating then removing the assert methods just for a slightly cleaner API.

As I agree about breaking code I'm inclined to close this with WontFix unless someone has strong feelings that it should be left open.

(Thanks Robert for the proposal - it's hard for me not to feel emotionally attached to the current API, which makes it correspondingly hard to be objective about it, but I appreciate people's desires to improve mock.)
Date User Action Args
2015-07-28 12:10:41michael.foordsetrecipients: + michael.foord, brett.cannon, rbcollins, carljm, poke, bignose, erik.bray, berker.peksag, kushal.das, ztane, fov, kevinbenton
2015-07-28 12:10:41michael.foordsetmessageid: <>
2015-07-28 12:10:41michael.foordlinkissue24651 messages
2015-07-28 12:10:40michael.foordcreate