-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Do Not Merge] RuntimeError if SYMPY_USE_CACHE='no' #9194
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge commit '41557f563821d9d77c71ed0edb23e80c00467b4c' into runtimeerror-if-no-cache
Revert "simplify Mul._eval_is_negative routine" This reverts commit 41557f5.
Merge commit '1c3b046c9831553dd18d98bcf5765c325df92eb6' into runtimeerror-if-no-cache
…ffb737d3209547fe6e76a9bb7845a0' into runtimeerror-if-no-cache
Revert "add _monotonic_sign and use in Add._eval_is_(pos, neg, npos, nneg)" This reverts commit d1a454a.
…ntimeError with SYMPY_USE_CACHE='no'] Merge branch 'master' into runtimeerror-if-no-cache
pzrq
changed the title
RuntimeError if SYMPY_USE_CACHE='no'
[Do Not Merge] RuntimeError if SYMPY_USE_CACHE='no'
Mar 24, 2015
Reproduced on master with no additional test files, just a console:
|
Generalised on #8266 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I do not want this merged as is, this is just a point to start the discussion on how to fix it as it makes it a lot harder to debug other issues I am trying to resolve.
Basically I have used the following file, which turns off the SymPy cache and runs a test from the existing solution:
https://gist.github.com/pzrq/05a5d1a16c63e7485110
The commit messages indicate the detected results in that I at least (Mac OSX, Python 2.7) am seeing stack traces that result in:
RuntimeError: maximum recursion depth exceeded
The first one seems to be attempting something like zero -> algebraic -> imaginary -> negative [then always recursively loops back to negative, the exact route depends on a shuffle].
I have not looked in detail at the second one, just ran the gist. Usage was just a variation on
python test.py
, fed intogit bisect
or other commands as needed.