On Wed, Apr 1, 2015 at 12:38 PM, Simon King <simon.k...@uni-jena.de> wrote: > Hi William, > > On 2015-04-01, William Stein <wst...@gmail.com> wrote: >>> That was new to me. Why Sage can not raise exception? >>> >>> >> Given the amount of confusion this causes I think we should discuss / >> consider changing this. > > That discussion should of course take place on sage-devel (not here),
Move to sage-devel. > but anyway: Is it a Python convention or a genuine SageMath convention > that comparison shouldn't raise an exception? Nils answered that it sort of was one, but the Python people realized it was a bad choice, and have moved away from it. A few years ago I would have (and did) argue for this convention (not raising exceptions). However, we *constantly* get support emails from people confused by this. As it is a major point of confusion, I am totally backing away from my previous stance, and think we should seriously considering making a change. > In the former case, we > shouldn't change it. And how much code would break if comparison was to > be allowed to raise exceptions? > > Best regards, > Simon > > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-supp...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
