RetroSearch Browse

Tue Jul 14 15:59:42 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140728.html

On Tue, Jul 14, 2015 at 11:51 PM, Florian Bruhin <me at the-compiler.org> wrote:
> However, it also has some special methods to see if it has been
> called:
>
>     >>> m.assert_called_with()
>     [...]
>     AssertionError: Expected call: mock()
>     Not called

I suppose it's too late to change this so these aren't methods... ISTM
the problem is this collision of usage on attribute lookup - on the
one hand, it's conjuring mock method calls, and on the other, it's
implementing methods of its own.

ChrisA

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

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

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