[issue24997] mock.call_args compares as equal and not equal

Berker Peksag added the comment: Correct, this has been fixed in issue 25195. Closing as 'out of date'. Thanks for triaging! -- nosy: +berker.peksag resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracke

[issue24997] mock.call_args compares as equal and not equal

Karthikeyan Singaravelan added the comment: Seems to have been implemented with ce913877e42b7fa03434c2e765ace891e0f5c4dc . https://bugs.python.org/issue25195 $ git checkout ce913877e42b7fa03434c2e765ace891e0f5c4dc~1 Lib/unittest/mock.py $ ./python.exe ../backups/bpo24997.py 1 True 2 True

[issue24997] mock.call_args compares as equal and not equal

Karthikeyan Singaravelan added the comment: Seems this is not reproducible at least on Python 3.6.4 and Master branch. # bpo24997.py from unittest.mock import * m = Mock() m(1,2) m.call_args print("1 ", m.call_args == call(1,2)) print("2 ", m.call_args != call(1,2)) # Master ./python.exe

[issue24997] mock.call_args compares as equal and not equal

Changes by Terry J. Reedy : -- nosy: +michael.foord, rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24997] mock.call_args compares as equal and not equal

New submission from A Kaptur: mock.call_args can be both equal to and not equal to another object: >>> m = Mock() >>> m(1,2) >>> m.call_args call(1, 2) >>> m.call_args == call(1,2) True >>> m.call_args != call(1,2) True This appears to be a recent regression - it repros on trunk, but not on 3.