[issue28911] Clarify the behaviour of assert_called_once_with

2017-02-23 Thread Arne de Laat
Changes by Arne de Laat <adel...@leukeleu.nl>: -- pull_requests: +222 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28911> ___ _

[issue28911] Clarify the behaviour of assert_called_once_with

2017-02-23 Thread Arne de Laat
Changes by Arne de Laat <adel...@leukeleu.nl>: -- pull_requests: +220 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28911> ___ _

[issue28911] Clarify the behaviour of assert_called_once_with

2017-02-23 Thread Arne de Laat
Changes by Arne de Laat <adel...@leukeleu.nl>: -- pull_requests: +219 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28911> ___ _

[issue28911] Clarify the behaviour of assert_called_once_with

2017-02-22 Thread Arne de Laat
Arne de Laat added the comment: *ping* Is this patch acceptable as is? Perhaps a new issue can be made for a method to check at most one call with a specific signature i.e. `assert_one_call_with`. -- ___ Python tracker <rep...@bugs.python.

[issue28911] Clarify the behaviour of assert_called_once_with

2017-01-19 Thread Arne de Laat
Arne de Laat added the comment: Unfortunately there cant be commas in the method name, that would clarify the name. It should be read as 'assert called once, with ...' not 'assert called once with ...'. I have often used the method to test something was called only once

[issue28911] Clarify the behaviour of assert_called_once_with

2016-12-08 Thread Arne de Laat
New submission from Arne de Laat: The name assert_called_once_with and the current method documentation can be interpreted to mean that it asserts that there is precisely one call matching the given signature, regardless of the total number of calls. However, the method first checks