Is there a philosophy for raising errors that guides the sympy development?
e.g. I passed an expression that couldn't be made into a polynomial to roots and roots handled that step for me...but didn't check to see if it succeeded or not so the error that I got came from something that roots called. The error ended up being "no symbol passed" rather than "cannot form polynomial" and was therefor confusing to me since I knew I passed a symbol. I would prefer to have an early error indicating failure rather than a later error. Any suggestions? /chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
