Todd Miller wrote:
So the two choices now on the table are:
- Change string equality comparisons to return an array of false or
true for objects which don't convert to strings. Change Numeric equality comparisons in a similar fashion.
- Special case string equality comparisons for None, as is done with
numerical comparisons. Raise a type error for objects (other than None) which don't convert to string arrays.
I think I like 2. Other opinions on 1 & 2? Other choices?
It would seem consistency with numerical arrays is important so unless someone presents a compelling argument for changing that behavior for arrays, the choice appears clear.
[wishing he had spent a little more time thinking about it and trying to remember why None is special cased for comparisons]