Wilfred Hughes <yowilf...@gmail.com> added the comment:
Note that this also affects the singledispatch library that backports
singledispatch to Python 2: https://github.com/python/typing/issues/484
--
nosy: +Wilfred.Hughes
___
Python tracke
New submission from Wilfred Hughes:
What steps will reproduce the problem?
from mock import Mock
m = Mock()
m(1, 2)
Mock name='mock()' id='139781492681104'
m.call_args == foob
Traceback (most recent call last):
File stdin, line 1, in module
File /home/wilfred/.py_envs/trifle/lib
Changes by Wilfred Hughes yowilf...@gmail.com:
--
title: Crash on comparing call_args with long strings - mock: Crash on
comparing call_args with long strings
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24857
Wilfred Hughes added the comment:
This caught me by surprise and I spent a while debugging due to this issue.
Isn't it reasonable that I can compare two values in Python without exceptions
being raised?
(1, 2) == foob
False
I'm happy to write a patch
Wilfred Hughes added the comment:
This bug is particularly subtle because it only applies to *long* strings.
m.call_args == f
False
m.call_args == fo
False
m.call_args == foo
False
m.call_args == foob
Traceback (most recent call last):
File stdin, line 1, in module
File build
New submission from Wilfred Hughes:
According to
https://wiki.python.org/moin/HowTo/Sorting/#Sort_Stability_and_Complex_Sorts
and Alex Martelli: http://stackoverflow.com/q/1915376/509706, Python's sorted()
is stable. It would be great to update the docs for sorted() to state