Kwankyu Lee wrote: > I expect that the comparison operators try to return mathematically > sensible result as far as it is practical (one systematic way is to > use coercion), and do something else (but still True or False) that is > clearly documented as soon as any difficulty you mentioned can arise.
What about <, <=, etc.? Do you agree that they should fail when rather than return a result with no mathematical meaning, even if the result is clearly documented? >> (3) "x != y" and "x == y" never raise an exception. >> >> Why? We are not talking about raising exceptions all the time, only >> in cases where it is likely that there is a bug... > > Because you mentioned TypeError as an option. Yes, sorry if I wasn't clear: what I'm aksing is what benefit you see of returning False instead of raising an error (in the case of !=). Thanks again, -- Marc -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
