[issue24857] Crash on comparing call_args with long strings

2015-08-13 Thread Michael Foord
Michael Foord added the comment: Oops, I misunderstood the bug report - however, call_args is a tuple, so you can't compare it directly to a string like that. Please refer to the docs on using call_args. -- ___ Python tracker

[issue24857] Crash on comparing call_args with long strings

2015-08-13 Thread Michael Foord
Michael Foord added the comment: call_args is not user settable! It is set for you by the mock when it is called. Arguably it could be a property instead. -- resolution: -> not a bug status: open -> closed ___ Python tracker

[issue24857] Crash on comparing call_args with long strings

2015-08-13 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +michael.foord stage: -> needs patch type: crash -> behavior versions: +Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___

[issue24857] Crash on comparing call_args with long strings

2015-08-13 Thread Wilfred Hughes
New submission from Wilfred Hughes: What steps will reproduce the problem? >>> from mock import Mock >>> m = Mock() >>> m(1, 2) >>> m.call_args == "foob" Traceback (most recent call last): File "", line 1, in File "/home/wilfred/.py_envs/trifle/lib/python2.7/site-packages/mock.py", line 2