-
-
Notifications
You must be signed in to change notification settings - Fork 65
Handle expressions not representable by SymPy #254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
TiagoCavalcante
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@hrueter, could you some examples in which this change has an impact? |
Even better would be to add a test. |
71081e7 to
93ed59e
Compare
|
@hreuter, is this PR still valid? |
You got my github handle wrong. ;-) I will check whether this is still relevant. But first some new bugs have to be fixed, so that I can run my old test problem again. |
e078418 to
f2e3df9
Compare
|
I have added tests for the three functions that I am fixing here. |
|
The added documentation text is a little bit rough. If you have suggestions to describe what these tests actually prove, let me know. |
Thanks. I will try to look at later today. |
|
LGTM - thanks. |
This deals with some cases where it is safe to return the expression, when it cannot be handled by SymPy.