Updates:
Status: Started
Labels: NeedsReview
Comment #4 on issue 2457 by matt...@gmail.com: gcd_terms trouble
http://code.google.com/p/sympy/issues/detail?id=2457
Pull request is here: https://github.com/sympy/sympy/pull/394
--
You received this message because you are
Updates:
Status: Fixed
Comment #5 on issue 2457 by smi...@gmail.com: gcd_terms trouble
http://code.google.com/p/sympy/issues/detail?id=2457
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To
Status: Accepted
Owner: smi...@gmail.com
Labels: Type-Defect Priority-Medium NeedsReview smichr
New issue 2462 by smi...@gmail.com: gcd_terms coeff absorbed
http://code.google.com/p/sympy/issues/detail?id=2462
The 2 arg mul behavior reabsorbs constants extracted from an Add so
Comment #6 on issue 2454 by smi...@gmail.com: Mul._eval_derivative should
use the quotient rule when possible
http://code.google.com/p/sympy/issues/detail?id=2454
Aaron, just using together gives a nicer result without using the quotient
rule:
n,d=x-1,(2*x+2)**2
Status: Accepted
Owner: hector1...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 2463 by hector1...@gmail.com: gcd and gcdex fails(misguides) in
case of decimal representation of integers
http://code.google.com/p/sympy/issues/detail?id=2463
gcd gives wrong answer and gcdex fails to
Status: Accepted
Owner: nicolas@gmail.com
Labels: Type-Enhancement Priority-Medium Solvers
New issue 2464 by nicolas@gmail.com: solve() should return sets, not
lists or None
http://code.google.com/p/sympy/issues/detail?id=2464
As discussed in issue 1694 and issue 1365, solve() should
Issue 1694: solve has many issues with fractions
http://code.google.com/p/sympy/issues/detail?id=1694
This issue is now blocking issue 2464.
See http://code.google.com/p/sympy/issues/detail?id=2464
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Comment #1 on issue 2461 by asmeurer: derived units infinite recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
It works for me. What Python version did you use?
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this
Comment #2 on issue 2461 by asmeurer: derived units infinite recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
Oh, never mind. I didn't notice that you called joule (I thought it was
just the import). Yes, I can reproduce this.
--
You received this message because you
Updates:
Labels: Printing
Comment #3 on issue 2461 by asmeurer: derived units infinite recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
I bisected it to
commit 08b4932810ab037fa5234b0b7b04a7de62aaed4a
Author: Mateusz Paprocki matt...@gmail.com
Date: Fri May 20
Comment #4 on issue 2461 by asmeurer: derived units infinite recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
And if you use the old ordering, it works:
$./bin/isympy -o old
IPython console for SymPy 0.6.7-git (Python 2.7.1) (ground types: gmpy)
These commands were
Comment #5 on issue 2461 by krastano...@gmail.com: derived units infinite
recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
It's likely that you have already noticed, but it affects only derived
units containing more than one base Unit.
--
You received this message
Status: Accepted
Owner: asmeurer
CC: smi...@gmail.com
Labels: Type-Defect Priority-Critical Milestone-Release0.7.0 Solvers
New issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
$./bin/test sympy/solvers/tests/test_solvers.py
Comment #1 on issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
Actually, that failure I showed is from an earlier commit when bisecting
(but it's later in the same test file, so it might still be a problem).
The real failure in
Comment #2 on issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
The tests pass in 32-bit.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send email to
Comment #3 on issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
The test is
solve(3*x+5+2**(-5*x+3), x) in [
[Rational(-5, 3) + LambertW(log(2**(-10240*2**(Rational(1,
3))/3)))/(5*log(2))],
[-Rational(5,3) +
Updates:
Labels: NeedsReview asmeurer
Comment #4 on issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
See https://github.com/sympy/sympy/pull/396.
--
You received this message because you are subscribed to the Google Groups
Comment #1 on issue 2464 by asmeurer: solve() should return sets, not lists
or None
http://code.google.com/p/sympy/issues/detail?id=2464
The return type of solve() has been discussed extensively on the mailing
list (for example,
Comment #2 on issue 2464 by asmeurer: solve() should return sets, not lists
or None
http://code.google.com/p/sympy/issues/detail?id=2464
Also, a possible future extension to support infinite solutions.
--
You received this message because you are subscribed to the Google Groups
Comment #6 on issue 2461 by krastano...@gmail.com: derived units infinite
recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
A more direct way to reproduce it is:
units.Unit(c_unit,c)*units.Unit(d_unit,d)
--
You received this message because you are subscribed to the
Updates:
Status: Started
Owner: matt...@gmail.com
Labels: Milestone-Release0.7.0
Comment #7 on issue 2461 by matt...@gmail.com: derived units infinite
recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
This is a simple bug in sort_key(). Minimal
Updates:
Labels: -Priority-Medium Priority-High
Comment #8 on issue 2461 by asmeurer: derived units infinite recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
(No comment was entered for this change.)
--
You received this message because you are subscribed to the
Updates:
Status: Fixed
Labels: -NeedsReview PassedReview
Comment #5 on issue 2465 by Vinzent.Steinberg: Test failure in solvers in
master
http://code.google.com/p/sympy/issues/detail?id=2465
Thanks, this is in now.
--
You received this message because you are subscribed to
Comment #9 on issue 2461 by ronan.l...@gmail.com: derived units infinite
recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
The problem Mateusz mentions is that kg itself appears inside
kg.sort_key(). But what causes the infinite recursion is the comparison 'kg
m'.
Comment #10 on issue 2461 by matt...@gmail.com: derived units infinite
recursion error
http://code.google.com/p/sympy/issues/detail?id=2461
So there are really two issues here. One is that when SymPy is unable to
compare to objects, it can enter infinite recursion. The other is
that
Comment #11 on issue 2461 by asmeurer: derived units infinite recursion
error
http://code.google.com/p/sympy/issues/detail?id=2461
So let's just replace any Basic object in the trees with the Python version
if there is one (like an int or a tuple), or else the string of the name of
the
Updates:
Status: Fixed
Labels: -NeedsReview PassedReview
Comment by asmeurer:
This was merged.
Affected issues:
issue 51: RootOf for polynomial equations
http://code.google.com/p/sympy/issues/detail?id=51
issue 2304: Remove Pure from top-level namespace
Status: Accepted
Owner: ronan.l...@gmail.com
CC: elliso...@gmail.com
Labels: Type-Defect Priority-Medium Milestone-Release0.7.0
New issue 2466 by ronan.l...@gmail.com: Units: meter second causes
infinite recursion
http://code.google.com/p/sympy/issues/detail?id=2466
This problem was
Comment #1 on issue 2466 by asmeurer: Units: meter second causes infinite
recursion
http://code.google.com/p/sympy/issues/detail?id=2466
The problem is that in relational.py we have:
if lhs.is_real and lhs.is_number and rhs.is_real and rhs.is_number:
return
Updates:
Blockedon: 2466
Comment #12 on issue 2461 by asmeurer: derived units infinite recursion
error
http://code.google.com/p/sympy/issues/detail?id=2461
See issue 2466. The fix there also fixes this.
We should still fix the problems with sort_key(), though.
--
You received this
Issue 2466: Units: meter second causes infinite recursion
http://code.google.com/p/sympy/issues/detail?id=2466
This issue is now blocking issue 2461.
See http://code.google.com/p/sympy/issues/detail?id=2461
--
You received this message because you are listed in the owner
or CC fields of this
Updates:
Cc: christian.muise
Labels: Assumptions
Comment #3 on issue 2466 by asmeurer: Units: meter second causes infinite
recursion
http://code.google.com/p/sympy/issues/detail?id=2466
Thinking about it, that line in Relational would also fail for any number
that doesn't
Status: Accepted
Owner: asmeurer
Labels: Type-Defect Priority-Medium
New issue 2467 by asmeurer: Better way to test if evalf() returns a Number
http://code.google.com/p/sympy/issues/detail?id=2467
If you run evalf(), you might think that you could test if it is a Number
by doing is_Number or
Comment #4 on issue 2466 by ronan.l...@gmail.com: Units: meter second
causes infinite recursion
http://code.google.com/p/sympy/issues/detail?id=2466
Setting is_number = False in Unit should solve this - it seems that this is
precisely what this attribute is for: distinguishing between
Comment #5 on issue 2466 by asmeurer: Units: meter second causes infinite
recursion
http://code.google.com/p/sympy/issues/detail?id=2466
We have
In [25]: x = Symbol('x', positive=True)
In [26]: x.is_number
Out[26]: False
Actually is_positive set is_real, not is_number. I'm not sure why
Comment #6 on issue 2466 by asmeurer: Units: meter second causes infinite
recursion
http://code.google.com/p/sympy/issues/detail?id=2466
It's because AtomicExpr sets is_number to be True, and units are
AtomicExprs. This is clearly wrong. I will remove that line from expr.py.
--
You
Updates:
Labels: NeedsReview asmeurer
Comment by asmeurer:
See https://github.com/sympy/sympy/pull/397. I made AtomicExpr.is_number
no longer return True by default, and robustified bool returning Relational
(this issue and the other were already fixed by the AtomicExpr fix, but
Status: Accepted
Owner: ronan.l...@gmail.com
Labels: Type-Defect Priority-High Milestone-Release0.7.0 Solvers
New issue 2468 by ronan.l...@gmail.com: ODE test failure in master
http://code.google.com/p/sympy/issues/detail?id=2468
(py_1.0)ronan@ronan-desktop:~/Projets/sympy-git$ py.test -k
Updates:
Labels: NeedsReview asmeurer
Comment #1 on issue 2468 by asmeurer: ODE test failure in master
http://code.google.com/p/sympy/issues/detail?id=2468
I can reproduce in 32-bit Python 2.6. The problem comes from a different
order of the solution. I'm surprised this hasn't come
Issue 1694: solve has many issues with fractions
http://code.google.com/p/sympy/issues/detail?id=1694
This issue is now blocking issue 2464.
See http://code.google.com/p/sympy/issues/detail?id=2464
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Updates:
Labels: NeedsReview asmeurer
Comment #4 on issue 2465 by asmeurer: Test failure in solvers in master
http://code.google.com/p/sympy/issues/detail?id=2465
See https://github.com/sympy/sympy/pull/396.
--
You received this message because you are subscribed to the Google Groups
Updates:
Status: Fixed
Labels: -NeedsReview PassedReview
Comment by asmeurer:
This was merged.
Affected issues:
issue 51: RootOf for polynomial equations
http://code.google.com/p/sympy/issues/detail?id=51
issue 2304: Remove Pure from top-level namespace
Updates:
Labels: NeedsReview asmeurer
Comment by asmeurer:
See https://github.com/sympy/sympy/pull/397. I made AtomicExpr.is_number
no longer return True by default, and robustified bool returning Relational
(this issue and the other were already fixed by the AtomicExpr fix, but
sympy.physics.mechanics?
+1
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, visit this
I was writing some documentation for physics/units.py and discovered
some infinite recursion RuntimeError:
from sympy.physics.units import joule
joule
File /home/luke/repos/sympy/sympy/core/expr.py, line 140, in __lt__
return C.StrictInequality(self, other)
File
Feel free to ask me to look at a branch. That's what I'm here for.
Additionally what is quality code is usually subject to the dev. If
it is PEP 8 compliant and doesn't have any major design flaws its
usually okay.
-- Andy
On Fri, Jun 3, 2011 at 7:45 PM, Aaron S. Meurer asmeu...@gmail.com
See the issue page. It has something to do with the new default lexicographic
ordering for printing.
Aaron Meurer
On Jun 8, 2011, at 2:20 AM, Luke wrote:
I was writing some documentation for physics/units.py and discovered
some infinite recursion RuntimeError:
from sympy.physics.units
Why is it necessary?
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, visit this group at
I think it's so that we can use symbols in boolean expressions, like
In [2]: x y
Out[2]: x ∧ y
But I think this is a bad design. We should rather have a BooleanSymbol to do
this.
Aaron Meurer
On Jun 8, 2011, at 2:41 PM, krastanov.ste...@gmail.com wrote:
Why is it necessary?
--
You
Think of it as a predicate -- it can be either true or false (hence
boolean).
On Jun 8, 2011 4:41 PM, krastanov.ste...@gmail.com
krastanov.ste...@gmail.com wrote:
Why is it necessary?
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this
On 8 June 2011 22:47, Haz christian.mu...@gmail.com wrote:
Think of it as a predicate -- it can be either true or false (hence
boolean).
Why it needs to be true or false? I don't expect the x in sin(x) to be
boolean. What am I missing?
On Jun 8, 2011 4:41 PM, krastanov.ste...@gmail.com
Why it needs to be true or false? I don't expect the x in sin(x) to be
boolean. What am I missing?
Nothing -- I misunderstood. Ronan may be able to shed some light:
-
https://github.com/sympy/sympy/commit/635d89c3c53fd84cc884e0ab62dc3f03480fe76a#sympy/core/symbol.py
Cheers
--
You
52 matches
Mail list logo
