realead added the comment:
@mark.dickinson
> ...my expectation was that there would be few cases of breakage, and that for
> those few cases it shouldn't be difficult to fix the breakage.
This expectation is probably correct.
My issue is somewhat only partly on-topic here: If o
realead added the comment:
This change makes life harder for people trying to get sane behavior with sets
for float-, complex- and tuple-objects containing NaNs. With "sane" meaning,
that
set([nan, nan, nan]) => {nan}
Until now, one has only to override the equal-compari
