Updates:
Status: Fixed
Labels: PassedReview
Comment #7 on issue 1075 by asmeurer: there should be a way to evaluate
sinh(1) to (-1/(2*E)+E/2)
http://code.google.com/p/sympy/issues/detail?id=1075
I reviewed it and pushed it in.
--
You received this message because you are subs
Comment #6 on issue 1075 by jezr...@gmail.com: there should be a way to
evaluate sinh(1) to (-1/(2*E)+E/2)
http://code.google.com/p/sympy/issues/detail?id=1075
rewrite has been fixed in this commit:
http://github.com/int3/sympy/commit/ca384bf4108d5a7f2c7564128c5784f27680f010
--
You received
Comment #5 on issue 1075 by asmeurer: there should be a way to evaluate
sinh(1) to (-1/(2*E)+E/2)
http://code.google.com/p/sympy/issues/detail?id=1075
(Re on the patch posted on the patches list)
I fixed some of these in issue 1448, but I guess I missed some. Looking
through git grep -C 1
Comment #3 on issue 1940 by asmeurer: Improvements for physical units
http://code.google.com/p/sympy/issues/detail?id=1940
I was just about to suggest using a dictionary instead of a tuple.
{'length':0} should be just as easy to work with
as Dimension(1, 0, 0, 0, 0, 0, 0, 0, 0), but it will b
Comment #2 on issue 1940 by harold.erbin: Improvements for physical units
http://code.google.com/p/sympy/issues/detail?id=1940
What do you think of using a dict for the dimension? I think it could be
easy to
continue to make dimensional analysis (we can imagine some functions or
whatever to
Issue 1941: Objects that know how to combine themselves
http://code.google.com/p/sympy/issues/detail?id=1941
This issue is now blocking issue 1336.
See http://code.google.com/p/sympy/issues/detail?id=1336
--
You received this message because you are listed in the owner
or CC fields of this issue
Updates:
Blockedon: 1941
Comment #11 on issue 1336 by asmeurer: Arbitrary constant type
http://code.google.com/p/sympy/issues/detail?id=1336
The better core idea is now issue 1941.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To pos
Status: Accepted
Owner: asmeurer
Labels: Type-Enhancement Priority-Medium
New issue 1941 by asmeurer: Objects that know how to combine themselves
http://code.google.com/p/sympy/issues/detail?id=1941
This is related to issue 1908. When I met with Ondrej last summer, we
worked on a core where
o
Issue 1908: more efficient core
http://code.google.com/p/sympy/issues/detail?id=1908
This issue is now blocking issue 1941.
See http://code.google.com/p/sympy/issues/detail?id=1941
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred
Updates:
Status: Accepted
Comment #1 on issue 1940 by asmeurer: Improvements for physical units
http://code.google.com/p/sympy/issues/detail?id=1940
I am not so sure if I like using the tuples for the units. It does
simplify the dimensional analysis, but it is not
extensible. For exa
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1940 by harold.erbin: Improvements for physical units
http://code.google.com/p/sympy/issues/detail?id=1940
I improved the old Unit class in order to add some physical properties and
comfort, like dimension, prefixes…
It works
Updates:
Labels: NeedsReview
Comment #1 on issue 1939 by asmeurer: Enhancements in ellipse class
http://code.google.com/p/sympy/issues/detail?id=1939
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" gr
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1939 by harold.erbin: Enhancements in ellipse class
http://code.google.com/p/sympy/issues/detail?id=1939
Some useful things were missing in the Ellipse class, such using the
eccentricity instead of one of radius to create the
Comment by timmy.horgan:
x**2
For more information:
http://code.google.com/p/sympy/wiki/TeXmacsInterface
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to sympy-iss...@googlegroups.com.
To unsubscribe from t
14 matches
Mail list logo