Repository navigation
Make Time equality comparison not raise an exception #2082
Description
As a follow-on to #1832 and #2081, this is a proposal to adjust Time comparisons so that == and != never raise exceptions. Instead if the comparison is made with an incompatible object (so an OperandTypeError gets raised), that would be caught and the comparison would return False (even for an array Time).
This behavior seems more natural and would fit with how numpy handles comparisons with mis-typed objects. This is an API change.
Activity
mhvk commentedon Feb 13, 2014
+1 (these comparisons were from a time I had only just started with python; it shows...)
astrofrog commentedon May 18, 2014
Re-scheduling to 1.0
mhvk commentedon Jul 11, 2014
This was solved by #2114, so closing.
embray commentedon Jul 11, 2014
When closing issues that are basically "won't fix" or "overcome by events" please also clear the milestone since the issue is no longer relevant to that milestone.