RetroSearch Browse

Fri Jul 17 03:50:40 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140789.html

On 17 Jul 2015 08:34, "Michael Foord" <fuzzyman at gmail.com> wrote:
>
>
>
> On Wednesday, 15 July 2015, Robert Collins <robertc at robertcollins.net>
wrote:
> > On 15 July 2015 at 12:59, Nick Coghlan <ncoghlan at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150717/ca214fdd/attachment-0001.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140789.html below:

[Python-Dev] How far to go with user-friendliness