On Tue, Jan 20, 2015 at 7:25 AM, Joachim Durchholz <[email protected]> wrote: > Am 19.01.2015 um 22:14 schrieb Amit Saha: >> >> I am of the same opinion too. The first impression that I get when I >> see NotImplementedError is that, it is not currently implemented and >> thus is probably a limitation of SymPy and not that it is perhaps not >> just possible to get the solution/answer. > > > Well, do we give a different error message for those problems that are > unsolvable? > Otherwise, the unsolvable ones are going to always give you > NotImplementedError.
Yes. I liked your idea of having a NoResult exception class. > > I'm assuming that SymPy does not even attempt to identify unsolvable > problems. If that is indeed true, "unsolvable" is a proper subset of "not > implemented", at least from SymPy's perspective, and SymPy does not > distinguish between the two. I am not sure if I would say "unsolveable" is a proper subset of "not implemented". The former I think is: mathematically, there is no solution. The latter: SymPy cannot do this currently. -- http://echorand.me -- You received this message because you are subscribed to the Google Groups "sympy" 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 http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CANODV3%3DGUkTiSUh-Uoeag2H6F0hf4tiq%3DvgCMbq-C8-eS6k4BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
