We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think the isequal behaviour has changed between SymPy 1.12 and the main branch.
isequal
With SymPy 1.13.dev:
>> isequal (vpa (1, 16), vpa (1, 32)) ans = 0
But on 1.12:
>> isequal (vpa (1, 64), vpa (1, 32)) ans = 1
In both cases:
>> vpa (1, 32) == vpa (1, 64) ans = (sym) True
Related: logspace is failing a test b/c of this.
The text was updated successfully, but these errors were encountered:
Partial workaround for isequal on vpa
645b491
Just get tests passing on recent SymPy, not really a fix yet (?). See Issue #1285.
Upstream issue: sympy/sympy#26146
Looks like their intention is that Float(1, 32) would not equal to Float(1, 64). Good.
Float(1, 32)
Float(1, 64)
(our == is more like SymPy Eq IIRC).
==
Eq
Sorry, something went wrong.
More tests about vpa inequality
16a2cb3
Related to Issue #1285, linked to the xtest. Probably waiting on upstream fix.
Successfully merging a pull request may close this issue.
I think the
isequal
behaviour has changed between SymPy 1.12 and the main branch.With SymPy 1.13.dev:
But on 1.12:
In both cases:
Related: logspace is failing a test b/c of this.
The text was updated successfully, but these errors were encountered: