Updates:
Status: Fixed
Labels: -NeedsReview
Comment #3 on issue 2576 by julien.r...@gmail.com: latex(1/x**2) should
return a \frac
http://code.google.com/p/sympy/issues/detail?id=2576
(No comment was entered for this change.)
--
You received this message because this project
Comment #1 on issue 3876 by julien.r...@gmail.com: latex inconsistent with
parentheses in powers
http://code.google.com/p/sympy/issues/detail?id=3876
Priority of exponents is from right to left (both for python and
mathematics), thus e.g. for (4**x)**y the parentheses are needed but for
Comment #1 on issue 3883 by smi...@gmail.com: powdenest should not do too
much
http://code.google.com/p/sympy/issues/detail?id=3883
Yes...this is a problem with many simplify functions as Matt Rocklin has
pointed out.
--
You received this message because this project is configured to
Comment #2 on issue 3882 by smi...@gmail.com: divisors() is not
type-consistent
http://code.google.com/p/sympy/issues/detail?id=3882
The simplest thing to do would be to have it work in ints like factorint
n = int(abs(n))
Working with Integer instead of int can significantly slow down some
Comment #2 on issue 3876 by asmeu...@gmail.com: latex inconsistent with
parentheses in powers
http://code.google.com/p/sympy/issues/detail?id=3876
I don't feel strongly that it should be either way, but the two printers
should be consistent.
--
You received this message because this
Comment #3 on issue 3882 by asmeu...@gmail.com: divisors() is not
type-consistent
http://code.google.com/p/sympy/issues/detail?id=3882
Internally it can use ints if they are faster. Only the return value needs
to be changed.
--
You received this message because this project is configured
Updates:
Status: Started
Owner: julien.r...@gmail.com
Labels: NeedsReview
Comment by julien.r...@gmail.com:
https://github.com/sympy/sympy/pull/2167
Affected issues:
issue 3740: Don't use \times in latex
http://code.google.com/p/sympy/issues/detail?id=3740
issue
Comment #4 on issue 3882 by smi...@gmail.com: divisors() is not
type-consistent
http://code.google.com/p/sympy/issues/detail?id=3882
this might be the way to go, then:
n = int(abs(n))
if isprime(n):
rv = [1, n]
elif n == 1:
rv = [1]
elif n == 0:
rv =
Comment #19 on issue 2014 by torstenm...@gmail.com: use ordered_iter or
iterable instead of checking for literal container
http://code.google.com/p/sympy/issues/detail?id=2014
Right, over 70. Shall I fix them in the way described? BTW, iter_ordered
now seems to be called is_sequence.
But
Updates:
Status: Fixed
Comment #6 on issue 3858 by smi...@gmail.com: Calling subs() on a logical
function sometimes returns bool type and
sometimes sympy.core.numbers.Zero/One type
http://code.google.com/p/sympy/issues/detail?id=3858
long issue has been fixed; simultaneous=True is
Comment #1 on issue 3884 by smi...@gmail.com: Polygon should raise an error
if sides cross
http://code.google.com/p/sympy/issues/detail?id=3884
the issue has to do with removal of collinear points; the first should be
Triangle((0,0),(3,2),(4,2)) and the second Segment((0,0),(1,0))
--
You
Comment #2 on issue 3812 by supp...@mooncoder.com: simplify(Implies) is
wrong
http://code.google.com/p/sympy/issues/detail?id=3812
Very annoying.
simplify_logic(Implies(a,b)) returns False too.
I found a workaround to first convert to_cnf() and then simplify.
--
You received this message
Comment #2 on issue 2695 by eric.the...@gmail.com: Pretty print of -x/y
http://code.google.com/p/sympy/issues/detail?id=2695
I may have a solution for this, to implement the first option (same width
fraction, but center slightly to the right instead of the default of
slightly to the left).
Comment #3 on issue 3812 by supp...@mooncoder.com: simplify(Implies) is
wrong
http://code.google.com/p/sympy/issues/detail?id=3812
Very annoying, silently gives wrong results...
simplify_logic(Implies(a,b)) returns False too.
I found a workaround: first call eliminate_implications() or
Comment #3 on issue 2695 by asmeu...@gmail.com: Pretty print of -x/y
http://code.google.com/p/sympy/issues/detail?id=2695
I don't have time to go into detail, but we have a guide at
https://github.com/sympy/sympy/wiki/development-workflow. GitHub also has
guides. If you need more help, just
Comment #3 on issue 3876 by asmeu...@gmail.com: latex inconsistent with
parentheses in powers
http://code.google.com/p/sympy/issues/detail?id=3876
By two printers, I mean the two pretty printers. str is another story. I
feel that x**(y**z) is a little easier to read than x**y**z, but I
Status: Valid
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 3885 by asmeu...@gmail.com: nullary functions should be allowed
http://code.google.com/p/sympy/issues/detail?id=3885
In [34]: f()
---
ValueError
I just feel that we are getting stuck with and spending too much time on
things that we shouldn't be taking this much time. Therefore, I request again
to all parties involved : Please voice your views/problems with these
structural changes suggested so that we can move ahead with things.
I
Hello,
I have just begun to explore SymPy and including a chapter on it in my
current book (which is on Python, Math and Science). I have just been
playing around with 0.7.2 version for Python 3 and have been able to run it
smoothly so far using CPython 3.3. So, thank you all.
I came across
Well alright. Since the discussion is supposed to be done publicly, I think
Sachin and I can discuss this on IRC. So, I have written an email to him
inviting him to IRC, today 21:00 IST.
Also, the API suggested by Stefan looks like something to go forward with,
albeit with some changes.
For
Lets get together on the irc one time today. Lets settle this so that we
can come to a consensus. Prasoon and I will be there in 1.5-2 hours. If
possible, @Stefan, do come online
On Wed, Jun 12, 2013 at 7:52 PM, Stefan Krastanov
krastanov.ste...@gmail.com wrote:
For the mutability issue :
For the mutability issue : Just as Aaron suggested, we do really need the
objects to be mutable. Doing something as
If I understand correctly, Aaron's main point was that mutability is
useful only in certain cases and I do not think that the current
module requires it. Most of the arguments in
Hello,
I am just getting started, so excuse the basic queries. Is there any
particular rule of thumb that explains the difference between together()
and the mathematical operator:
x/y-y/x
x/y - y/x
together(x/y-y/x)
(x**2 - y**2)/(x*y)
Thanks,
Amit.
--
You received this message because
On Wednesday, June 12, 2013 7:52:34 PM UTC+5:30, Stefan Krastanov wrote:
For the mutability issue : Just as Aaron suggested, we do really need
the
objects to be mutable. Doing something as
If I understand correctly, Aaron's main point was that mutability is
useful only in certain
I would guess that there is not going to be a big interface change before
the next release. At least nobody is working on it as far as I know. And
much of the mess will be ironed out inside, I would think, so even when
it all works better there shouldn't be a huge change. Eventually we want a
Stefan,
I just read through your proposed API. In general it seems reasonable but
Luke, Gilbert and I spoke last night on irc (logs:
http://colabti.org/irclogger/irclogger_log/sympy?date=2013-06-12) about how
to deal with immutability/mutability, subclassing from Basic/Expr, and
garbage in/out.
I'm struggling with the most direct route to use a time series numpy array
to get a time series back from a SymPy equation.
Ideally I'd like to call something like sol.evalf(x), but that doesn't
work. I have a loop structure that does it at present, but the continual
reconstructing a dict
Use lambdify().
Aaron Meurer
On Wed, Jun 12, 2013 at 1:06 PM, Shawn Garbett shawn.garb...@gmail.com wrote:
I'm struggling with the most direct route to use a time series numpy array
to get a time series back from a SymPy equation.
Ideally I'd like to call something like sol.evalf(x), but
On Wednesday, June 12, 2013 4:54:21 PM UTC-5, Aaron Meurer wrote:
Use lambdify().
I've just spent a couple hours fiddling with lambdify(). I can't seem to
get it to work. First of all, lambdify requires that one specify the args
for the first argument. I'm trying to write this to deal with
It may be that we don't understand your application given your example.
From your example I suspect you want to compute something like the
following
In [1]: from sympy import *
In [2]: s4 = Symbol('s4')
In [3]: s6 = Symbol('s6')
In [4]: sol = 1.0e-6*s4 + 1.0e-12*s6
In [5]: sol
Out[5]: 1.0e-6*s4
30 matches
Mail list logo
