John W. added the comment:
This got a little discussion over at
http://lists.idyll.org/pipermail/testing-in-python/2017-February/007012.html
The current evidence seem to indicate this is indeed a bug in the
implementation of assert_has_calls
John W. added the comment:
This also seems to apply to unittest.mock in Python3.4.
I described my similar issue on SO:
http://stackoverflow.com/questions/42212433/what-is-wrong-with-this-simple-py-test-use-case
It seems like it may be the same issue described here.
For reference, this is my
John W. O'Brien added the comment:
For reference:
CPython code comments showing that this may be an anticipated problem:
http://hg.python.org/cpython/file/0830670a9d9d/Lib/test/support/__init__.py#l562
An example of another project that seems to have tackled this problem in the
way neologix
New submission from John W. Shipman j...@nmt.edu:
optparse's .parse_args() method has a 'values=...' keyword argument
that is documented as:
'object to store option arguments in (default: a new instance of
optparse.Values)'
There is no description of what types this argument may have
