Comment #11 on issue 1678 by jorn.baayen: [PATCH] latex: Format
higher-degree roots using \sqrt[deg]{x}
http://code.google.com/p/sympy/issues/detail?id=1678
Issue 1691 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this
Updates:
Status: Fixed
Comment #5 on issue 1700 by Vinzent.Steinberg: [PATCH] Add latex printer
for Poly class
http://code.google.com/p/sympy/issues/detail?id=1700
This change is trivial, so I pushed it in.
--
You received this message because you are listed in the owner
or CC fields
Updates:
Status: Fixed
Labels: -NeedsReview
Comment #12 on issue 1678 by Vinzent.Steinberg: [PATCH] latex: Format
higher-degree roots using \sqrt[deg]{x}
http://code.google.com/p/sympy/issues/detail?id=1678
Jorn, you're also one of the developers, feel free to review any
Comment #3 on issue 1699 by Vinzent.Steinberg: result of sympify(None) and
others
http://code.google.com/p/sympy/issues/detail?id=1699
It's in.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your
Updates:
Labels: -NeedsReview
Comment #11 on issue 1685 by Vinzent.Steinberg: Wrong result from
collect(...) in simplify.py
http://code.google.com/p/sympy/issues/detail?id=1685
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Status: Fixed
Comment #2 on issue 1687 by Vinzent.Steinberg: gosper had variable name
errors
http://code.google.com/p/sympy/issues/detail?id=1687
It's in I think.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #7 on issue 1680 by ronan.l...@gmail.com: Infinite recursion in cos
(and other trigonometric functions)
http://code.google.com/p/sympy/issues/detail?id=1680
There's some hackish stuff in simplify/cse_opts.py that predates
.could_extract_minus_sign() and should be reworked completely
Comment #8 on issue 1680 by asmeurer: Infinite recursion in cos (and other
trigonometric functions)
http://code.google.com/p/sympy/issues/detail?id=1680
The problem with different architectures is that Python's hash() function
gives different results for hashable objects
on different
Comment #35 on issue 1671 by smichr: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
All docstrings now pass on Windows.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred
Updates:
Cc: ondrej.certik
Comment #1 on issue 1701 by asmeurer: ode.py: xpassing test
http://code.google.com/p/sympy/issues/detail?id=1701
The test XPasses for me, too, though I am not sure what exact architecture
my machine is running under at this
point. Ondrej's buildbots are
Updates:
Status: Fixed
Labels: -NeedsReview
Comment #10 on issue 1667 by Vinzent.Steinberg: Unexpected behaviour when
calling Sum.doit().
http://code.google.com/p/sympy/issues/detail?id=1667
Thank you, this is in.
--
You received this message because you are listed in the
Comment #2 on issue 1701 by Vinzent.Steinberg: ode.py: xpassing test
http://code.google.com/p/sympy/issues/detail?id=1701
Run this to be sure:
import sys
from math import *
log(sys.maxint, 2)
63.0
(The 64th bit is for the sign.)
--
You received this message because you are listed in the
Updates:
Status: Started
Cc: fab...@fseoane.net fredrik.johansson
Comment #8 on issue 1501 by Vinzent.Steinberg: documentation day issues
http://code.google.com/p/sympy/issues/detail?id=1501
resp. means respectively I think. I thought you could use it in this
context, but I'm
Updates:
Labels: -NeedsReview
Comment #9 on issue 1501 by Vinzent.Steinberg: documentation day issues
http://code.google.com/p/sympy/issues/detail?id=1501
I pushed your changes in.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Status: Accepted
Owner: smichr
Labels: Type-Defect Priority-Medium
New issue 1702 by smichr: crlf
http://code.google.com/p/sympy/issues/detail?id=1702
Since code quality checks for \r\n in a file, should strip_whitespace be
made to handle this correction?
--
You received this message because
Comment #4 on issue 1701 by Vinzent.Steinberg: ode.py: xpassing test
http://code.google.com/p/sympy/issues/detail?id=1701
My Python is being run as just slightly less than 32-bits.
Floating-point arithmetic makes it possible. :)
I don't think there's a difference between Intel and AMD, it's
Comment #5 on issue 1701 by asmeurer: ode.py: xpassing test
http://code.google.com/p/sympy/issues/detail?id=1701
import sys
sys.maxint
2147483647
2**31
2147483648L
It's actually 1 less than 2**31, because 0 is positive.
Which leads to another easier way to check, just type 2**31 and see if
Updates:
Status: Fixed
Labels: -NeedsReview
Comment #4 on issue 1699 by Vinzent.Steinberg: result of sympify(None) and
others
http://code.google.com/p/sympy/issues/detail?id=1699
(No comment was entered for this change.)
--
You received this message because you are listed in
Comment #38 on issue 1671 by smichr: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
re symbols...I just used a find a replace to change most of them. There are
some,
especially those with assumptions, that remain.
rebasing is finished,
Comment #39 on issue 1671 by asmeurer: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
This still does not work for me:
dhcp-baca-10:sympy aaronmeurer((8cfa7c2...)$)$./bin/test
Traceback (most recent call last):
File ./bin/test, line
Comment #40 on issue 1671 by smichr: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
please try again...I added and committed the file. I don't think I did the
commit before.
--
You received this message because you are listed in the
Comment #41 on issue 1671 by smichr: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
I'm wondering if we might put in two options into doctest:
-n --normal this would run a normal doctest (as stlid would run)
-s --star this would
Issue 353: piecewise functions
http://code.google.com/p/sympy/issues/detail?id=353
This issue is no longer blocking issue 1695.
See http://code.google.com/p/sympy/issues/detail?id=1695
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #37 on issue 1695 by asmeurer: integral of a piecewise function
gives bad result
http://code.google.com/p/sympy/issues/detail?id=1695
By the way, your pact doesn't seem to apply to the latest master.
Something in commit
02568ad3e34cafa1c563c12254d6b988c9de6dba seems to have broken
Comment #42 on issue 1671 by smichr: runtests modifications and docstring
corrections
http://code.google.com/p/sympy/issues/detail?id=1671
After working on this issue for some time now, I leave a few notes. I'm not
sure if
here or in the commit message is the best place to put them.
[*] I
25 matches
Mail list logo
