Updates:
Labels: Milestone-Release0.7.0 NeedsReview
Comment #7 on issue 2354 by matt...@gmail.com: isympy -o doesn't parse bad
arguments correctly
http://code.google.com/p/sympy/issues/detail?id=2354
Pull request is here: https://github.com/sympy/sympy/pull/348
--
You received this
Updates:
Status: Accepted
Cc: smi...@gmail.com nicolas@gmail.com
Labels: Solvers Assumptions
Comment #1 on issue 2410 by asmeurer: Setting range for variables
http://code.google.com/p/sympy/issues/detail?id=2410
Support for solving inequalities has been added since
Comment #22 on issue 1620 by asmeurer: Allow derivatives of unknown
functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
It might work. That is actually what Maple's eval() function is from
comment 2.
--
You received this message because you are subscribed
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2416 by andreas@googlemail.com: Exponential function
exp(I*k**2*pi) simplifies to -1
http://code.google.com/p/sympy/issues/detail?id=2416
This should not simplify to -1, since it is 1 for even k and -1 for odd k:
In
Comment #1 on issue 2413 by asmeurer: Printing performance (_compare_pretty)
http://code.google.com/p/sympy/issues/detail?id=2413
If you were not printing anything, what was calling _compare_pretty()? By
the way, that function is deprecated, and should be replaced with
Basic.sort_key().
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #3 on issue 2415 by asmeurer: Poly(x, x) * I != I * Poly(x, x)
http://code.google.com/p/sympy/issues/detail?id=2415
This is just because Expr.__mul__ eats up the Poly. To play it safe, you
should always to
Updates:
Labels: -Milestone-Release0.7.0 Milestone-Release0.7.1
Comment #6 on issue 2406 by asmeurer: improve Tuple constructor
http://code.google.com/p/sympy/issues/detail?id=2406
I don't understand how from_iter would fix the *args problem. Are you
suggesting to change the
Issue 2402: integration3-backport
http://code.google.com/p/sympy/issues/detail?id=2402
This issue is now blocking issue 2010.
See http://code.google.com/p/sympy/issues/detail?id=2010
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Updates:
Status: Fixed
Comment #2 on issue 2402 by asmeurer: integration3-backport
http://code.google.com/p/sympy/issues/detail?id=2402
Mateusz's branch was pushed in.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this
Updates:
Blockedon: 2402
Comment #15 on issue 2010 by asmeurer: Integration with the full Risch
Algorithm
http://code.google.com/p/sympy/issues/detail?id=2010
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Updates:
Cc: jensen.o...@gmail.com
Comment #3 on issue 2414 by asmeurer: [Feature request] Deferred expressions
http://code.google.com/p/sympy/issues/detail?id=2414
Other kinds expressions have their unevaluated equivalents.
I think maybe am not understanding you fully because I am not
Updates:
Status: Accepted
Labels: WrongResult
Comment #1 on issue 2416 by asmeurer: Exponential function exp(I*k**2*pi)
simplifies to -1
http://code.google.com/p/sympy/issues/detail?id=2416
(No comment was entered for this change.)
--
You received this message because you
Comment #7 on issue 2406 by ronan.l...@gmail.com: improve Tuple constructor
http://code.google.com/p/sympy/issues/detail?id=2406
@renato: If there's precedent from 'fromiter', I guess it's a better choice.
@Aaron: the convention would be changed from expr.__class__(*expr.args) to
Updates:
Cc: ronan.l...@gmail.com
Labels: Assumptions
Comment #2 on issue 2416 by asmeurer: Exponential function exp(I*k**2*pi)
simplifies to -1
http://code.google.com/p/sympy/issues/detail?id=2416
It's because of
In [15]: k = Symbol('k', integer=True)
In [16]:
Comment #3 on issue 2413 by asmeurer: Printing performance (_compare_pretty)
http://code.google.com/p/sympy/issues/detail?id=2413
Of course it isn't different for me. But reproducing something from a
plain English description isn't very easy. A stack trace would help a
lot. Some code
Updates:
Labels: NeedsReview mattpap
Comment #3 on issue 2409 by asmeurer: variable undefined
http://code.google.com/p/sympy/issues/detail?id=2409
It looks like a fix for this is at https://github.com/sympy/sympy/pull/345.
--
You received this message because you are subscribed to the
Comment #8 on issue 2406 by asmeurer: improve Tuple constructor
http://code.google.com/p/sympy/issues/detail?id=2406
I see.
Well, I still think that Tuple should act like it does now, and that we
should create some conversion function to convert iterables to Tuples
(sympify() would call
Comment #4 on issue 2413 by five...@gmail.com: Printing performance
(_compare_pretty)
http://code.google.com/p/sympy/issues/detail?id=2413
import sympy
x = sympy.Symbol('x')
print sympy.ccode(x**2 + 1)
(Pdb) bt
/home/jed/src/sympy/sympy/a.py(4)module()
- print sympy.ccode(x**2 + 1)
Updates:
Labels: NeedsReview Ronan.Lamy
Comment #11 on issue 2338 by asmeurer: Use predicates and propositions
instead of Assume objects
http://code.google.com/p/sympy/issues/detail?id=2338
Correct me if I am wrong, but I think these fixes are at
Comment #6 on issue 2388 by asmeurer: The value of str(expr) depends on a
global setting
http://code.google.com/p/sympy/issues/detail?id=2388
OK, so two questions:
- Should repr() be the same?
- Should __repr__ call srepr()? Right now, it calls sstr() (the same as
__str__).
I'll
Updates:
Blockedon: 2417
Comment #7 on issue 2388 by asmeurer: The value of str(expr) depends on a
global setting
http://code.google.com/p/sympy/issues/detail?id=2388
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google
Comment #9 on issue 2388 by matt...@gmail.com: The value of str(expr)
depends on a global setting
http://code.google.com/p/sympy/issues/detail?id=2388
Of course please swap srepr() with sstr(). It should read It calls sstr()
because of a bug in Python. If you change Basic.__repr__ to call
Comment #10 on issue 2388 by asmeurer: The value of str(expr) depends on a
global setting
http://code.google.com/p/sympy/issues/detail?id=2388
I see. Well, that's incredibly stupid. Do the Python guys know about this?
--
You received this message because you are subscribed to the Google
Comment #11 on issue 2388 by matt...@gmail.com: The value of str(expr)
depends on a global setting
http://code.google.com/p/sympy/issues/detail?id=2388
Yes, it is. Ondrej asked about this on python-dev:
http://mail.python.org/pipermail/python-dev/2008-July/081562.html
There is also a
Updates:
Status: Fixed
Labels: -NeedsReview -Milestone-Release0.7.1 -mattpap PassedReview
Comment #15 on issue 1868 by matt...@gmail.com: solve(floating point, x)
stopped working
http://code.google.com/p/sympy/issues/detail?id=1868
The other part (comment #4) still needs
Comment #6 on issue 2413 by five...@gmail.com: Printing performance
(_compare_pretty)
http://code.google.com/p/sympy/issues/detail?id=2413
_compare_pretty original:
9.673 real 9.453 user 0.110 sys 98.85 cpu
_compare_pretty skipping match:
5.380 real 5.170 user 0.123 sys 98.37
Updates:
Summary: solve and solve_poly_system can give ambiguous results
Comment #2 on issue 2405 by smi...@gmail.com: solve and solve_poly_system
can give ambiguous results
http://code.google.com/p/sympy/issues/detail?id=2405
There is a reason that the solver's current
Comment #3 on issue 2405 by smi...@gmail.com: solve and solve_poly_system
can give ambiguous results
http://code.google.com/p/sympy/issues/detail?id=2405
OK, here is where solve_poly_system is ambiguous (like solve):
h[1] from sympy.solvers.polysys import solve_poly_system as so
Comment #4 on issue 2405 by matt...@gmail.com: solve and solve_poly_system
can give ambiguous results
http://code.google.com/p/sympy/issues/detail?id=2405
There will be always some ambiguity as long as solvers aren't returning
mappings. However, it's not solve_poly_system() where the
Updates:
Status: Fixed
Labels: -NeedsReview PassedReview
Comment #15 on issue 2386 by asmeurer: gosper(...) is missing tests and
docstring
http://code.google.com/p/sympy/issues/detail?id=2386
And the NotImplementedError patch was pushed in.
--
You received this message
Updates:
Summary: Put all printing orderings in one central location
Labels: -Milestone-Release0.7.0 -NeedsReview PassedReview
Comment #8 on issue 2354 by asmeurer: Put all printing orderings in one
central location
http://code.google.com/p/sympy/issues/detail?id=2354
This
Issue 2354: Put all printing orderings in one central location
http://code.google.com/p/sympy/issues/detail?id=2354
This issue is no longer blocking issue 1491.
See http://code.google.com/p/sympy/issues/detail?id=1491
--
You received this message because you are listed in the owner
or CC fields
Updates:
Blockedon: -2354
Comment #32 on issue 1491 by asmeurer: Remove old printing ordering at some
point
http://code.google.com/p/sympy/issues/detail?id=1491
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Comment #9 on issue 2406 by renato.c...@gmail.com: improve Tuple constructor
http://code.google.com/p/sympy/issues/detail?id=2406
So for now we are:
1. sympifying arguments to Tuple
2. sympify(tuple()) - Tuple()
3. adding method fromiter() to Tuple()
4. keep Tuple([x, y, z]) - Tuple([x, y, z])
Status: Accepted
Owner: asmeurer
Labels: Type-Defect Priority-Medium
New issue 2418 by asmeurer: Interval.evalf() returns a mpmath interval
http://code.google.com/p/sympy/issues/detail?id=2418
This was originally my idea, but I see now that it was probably a bad one.
We have:
In [1]:
Updates:
Labels: EasyToFix
Comment #1 on issue 2418 by asmeurer: Interval.evalf() returns a mpmath
interval
http://code.google.com/p/sympy/issues/detail?id=2418
This will be easy to fix. Just make .evalf() return Interval(*([i.evalf()
for i in a.args[:2]] + list(a.args[2:]))).
Comment #10 on issue 2406 by asmeurer: improve Tuple constructor
http://code.google.com/p/sympy/issues/detail?id=2406
Yes, just do it from the outset, i.e., #3 should be adding method
fromiter() to Basic.
And the rest are correct too.
--
You received this message because you are subscribed
Updates:
Labels: Ronan.Lamy
Comment #6 on issue 2385 by asmeurer: Refactor Basic.sorted_key
http://code.google.com/p/sympy/issues/detail?id=2385
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
38 matches
Mail list logo