Updates:
Status: WontFix
Comment #23 on issue 391 by ronan.l...@gmail.com: naming for subclasses of
Function ?
http://code.google.com/p/sympy/issues/detail?id=391
Our conventions work fine and any change would be disruptive, so I agree
that we should leave things as they are.
--
Updates:
Status: WontFix
Comment #3 on issue 366 by ronan.l...@gmail.com: Interactive plotting with
pygame
http://code.google.com/p/sympy/issues/detail?id=366
Current thinking is that plotting should be handled by matplotlib, so we
won't use pygame and we won't extend the current
Updates:
Status: WontFix
Comment #6 on issue 454 by ronan.l...@gmail.com: __lt__ should work in the
pythonic way
http://code.google.com/p/sympy/issues/detail?id=454
We've settled on x y returning x y and I don't think that'll change.
--
You received this message because you are
Updates:
Cc: krastano...@gmail.com
Comment #4 on issue 366 by asmeu...@gmail.com: Interactive plotting with
pygame
http://code.google.com/p/sympy/issues/detail?id=366
Actually current thinking is at plotting should be backend agnostic, with a
main focus on matplotlib, so Pharos
Comment #5 on issue 366 by krastano...@gmail.com: Interactive plotting with
pygame
http://code.google.com/p/sympy/issues/detail?id=366
Making this a backend for the plotting module is possible. However WontFix
seems appropriate as I doubt that there will be much interest in this
option
Updates:
Status: Invalid
Comment #2 on issue 684 by ronan.l...@gmail.com: speed: Rational is slow
http://code.google.com/p/sympy/issues/detail?id=684
It's unclear what the issue was here. I doubt it's still relevant.
--
You received this message because you are subscribed to the Google
Updates:
Status: Valid
Labels: WrongResult Core
Comment #1 on issue 1516 by ronan.l...@gmail.com: exp.as_leading_term
returns wrong results
http://code.google.com/p/sympy/issues/detail?id=1516
This is still valid.
--
You received this message because you are subscribed to
Updates:
Status: Fixed
Comment #11 on issue 588 by ronan.l...@gmail.com: simplify should be better
at detecting repeated factors
http://code.google.com/p/sympy/issues/detail?id=588
It seems that this has been fixed.
--
You received this message because you are subscribed to the
Updates:
Status: Fixed
Comment #4 on issue 3268 by smi...@gmail.com: simplify fails to recognize a
zero
http://code.google.com/p/sympy/issues/detail?id=3268
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Status: Valid
Owner:
Labels: Type-Defect Priority-Medium
New issue 3271 by smi...@gmail.com: simplify doesn't handle expressions
like 2**(2*x+2)/4 well
http://code.google.com/p/sympy/issues/detail?id=3271
Somewhere in simplify, expression that contain numerical terms that are
combined
When I have absolutely no idea where to start I just create a file
called temp.py somewhere and start writing the functionality. If after
having some code you still do not know where to put it, just send a
pull request (very much preferable aver patches) with the temp.py file
and we will help.
Hello,
On Mon, May 21, 2012 at 7:32 PM, Saurabh Jha saurabh.j...@gmail.com wrote:
Should I implement the sub- functions first and send them as patches
or something else.
I usually go through the plan of the features I plan to implement and
pick one which looks small enough to be independent.
Absolutely. The more discussion that happens publicly (i.e., on the
list, or the issue tracker/pull requests), the better, because then
the community will be involved in the project and can give any
additional input that they may have (and it will also make it easier
to track your progress
13 matches
Mail list logo
