On 17 Jul 2015 08:34, "Michael Foord" <fuzzy...@gmail.com> wrote: > > > > On Wednesday, 15 July 2015, Robert Collins <robe...@robertcollins.net> wrote: > > On 15 July 2015 at 12:59, Nick Coghlan <ncogh...@gmail.com> wrote: > >> > >> There is zero urgency here, so nothing needs to change for 3.5. > >> Robert's plan is a fine one to propose for 3.6 (and the PyPI mock > >> backport). > > > > Right - the bad API goes back to the very beginning. I'm not planning > > > I disagree it's a bad api. It's part of why mock was so easy to use and part of why it was so successful. With the new check for non-existent assert methods it's no longer dangerous and so doesn't need fixing.
Could you help me understand how the presence of assert... on the mock vs in the mock module affected ease of use? -Rob
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
