On Thu, Jan 15, 2015 at 2:42 AM, Aaron Meurer <[email protected]> wrote: > > > On Wed, Jan 14, 2015 at 3:28 AM, Joachim Durchholz <[email protected]> wrote: >> >> Am 13.01.2015 um 23:53 schrieb Aaron Meurer: >>> >>> Returning [] instead of raising NotImplementedError would probably not be >>> a >>> bad idea either >> >> >> That would be confusable with a "we know that there is no solution" (1) >> result. >> In this case, we have a "we do not know what solutions exit" (2) result, >> which should be represented in a clearly distinguishable fashion (both on >> the console output and to other code). >> An exception should be a "the software has failed" result (3). >> >> SymPy currently does not distinguish between (2) and (3) and reports >> everything as a failure. > > > No, SymPy cannot distinguish (1) and (2). If the software failed you should > get an exception that isn't NotImplementedError.
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. -- 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/CANODV3n_mLXxBL9s7wEYgd428sYL2dvbB-7Jpb7ALawLu30nPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
