Comment #1 on issue 3526 by skirpic...@gmail.com: Fuzzy and untranslated
strings in Russian translation of the tutorial.
http://code.google.com/p/sympy/issues/detail?id=3526
https://github.com/sympy/sympy/pull/1949
--
You received this message because this project is configured to send all
Comment #42 on issue 1235 by kot.bege...@gmail.com: Problem installing in
Windows
http://code.google.com/p/sympy/issues/detail?id=1235
Folks, I dont understand what the issue is. I've just created .exe and .msi
installers, and they work just fine on win7/64.
python setup.py build
Comment #43 on issue 1235 by asmeu...@gmail.com: Problem installing in
Windows
http://code.google.com/p/sympy/issues/detail?id=1235
The problem is that you have to be using Windows to do that. Or are you not?
--
You received this message because this project is configured to send all
Issue 3622: Support for gmpy and gmpy2.
http://code.google.com/p/sympy/issues/detail?id=3622
This issue is now blocking issue sympy:3652.
See http://code.google.com/p/sympy/issues/detail?id=3652
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Updates:
Labels: -Priority-Medium Priority-High
Blockedon: sympy:3622
Comment #1 on issue 3652 by asmeu...@gmail.com: Make sure classes play nice
with potential subclasses
http://code.google.com/p/sympy/issues/detail?id=3652
Issue 3622 is another big anti-pattern that we
Comment #5 on issue 3599 by asmeu...@gmail.com: Apply 2to3 idioms fixer
to code base
http://code.google.com/p/sympy/issues/detail?id=3599
type(x) is (almost) synonymous with x.func in SymPy, so we should also go
through check for A.func is ... or A.func in ... too. This is related
to
Issue 3622: Support for gmpy and gmpy2.
http://code.google.com/p/sympy/issues/detail?id=3622
This issue is no longer blocking issue sympy:3652.
See http://code.google.com/p/sympy/issues/detail?id=3652
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Issue 3599: Apply 2to3 idioms fixer to code base
http://code.google.com/p/sympy/issues/detail?id=3599
This issue is now blocking issue sympy:3652.
See http://code.google.com/p/sympy/issues/detail?id=3652
--
You received this message because you are listed in the owner
or CC fields of this
Comment #44 on issue 1235 by kot.bege...@gmail.com: Problem installing in
Windows
http://code.google.com/p/sympy/issues/detail?id=1235
I can volunteer for win64 image creation.
Another possible option is running MS-provided vhd image under Virtual Box
on linux:
Comment #45 on issue 1235 by asmeu...@gmail.com: Problem installing in
Windows
http://code.google.com/p/sympy/issues/detail?id=1235
If the virtualbox thing can be completely automated, then let's do that. We
really don't have the resources to do release processes that cannot be
Updates:
Blockedon: sympy:3445
Comment #46 on issue 1235 by asmeu...@gmail.com: Problem installing in
Windows
http://code.google.com/p/sympy/issues/detail?id=1235
(No comment was entered for this change.)
--
You received this message because this project is configured to send all
Issue 3445: Automate the release process
http://code.google.com/p/sympy/issues/detail?id=3445
This issue is now blocking issue sympy:1235.
See http://code.google.com/p/sympy/issues/detail?id=1235
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Status: New
Owner:
Labels: Type-Defect Priority-Medium Integration
New issue 3732 by gra...@gmail.com: Integration of Piecewise function
should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
Currently,
from sympy import *
from sympy.abc import x
q =
Updates:
Status: NeedsDecision
Comment #1 on issue 3732 by asmeu...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
This requires some thought. What is the reason that you would prefer it to
be this way?
Comment #3 on issue 3732 by gra...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
https://github.com/sympy/sympy/pull/1971
--
You received this message because this project is configured to send all
issue
Comment #2 on issue 3732 by asmeu...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
https://github.com/sympy/sympy/pull/1971
--
You received this message because this project is configured to send all
issue
Comment #4 on issue 3732 by gra...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
I agree with you on that case, but I guess the mathematical motivation for
the fact that integration of any function(provided
Comment #5 on issue 3732 by gra...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
Also, let's say I have a piecewise function p and we expect to get the
value of its integral at x = 4, then we should expect q
Comment #6 on issue 3732 by asmeu...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
There is no such thing as the value of an integral at a point. It's only
defined up to a step function. So the question is how to
Comment #7 on issue 3732 by gra...@gmail.com: Integration of Piecewise
function should also be continuous
http://code.google.com/p/sympy/issues/detail?id=3732
Sorry for not using the exact mathematical language. I meant value of the
function q which is the anti-derivative of p at x =
Comment #1 on issue 3717 by smi...@gmail.com: Factors needs better -1
processing
http://code.google.com/p/sympy/issues/detail?id=3717
The following also raises an error: `simplify(1/(1 + sqrt(2)*I))`
That is also fixed by the PR
--
You received this message because this project is
Issue 1766: separatevars should use expand [was: expand(power_base=True)
is too aggressive]
http://code.google.com/p/sympy/issues/detail?id=1766
This issue is now blocking issue sympy:1745.
See http://code.google.com/p/sympy/issues/detail?id=1745
--
You received this message because you are
Issue 1766: separatevars should use expand [was: expand(power_base=True)
is too aggressive]
http://code.google.com/p/sympy/issues/detail?id=1766
This issue is now blocking issue sympy:1745.
See http://code.google.com/p/sympy/issues/detail?id=1745
--
You received this message because you are
Comment #9 on issue 1234 by smi...@gmail.com: solve() should give all
solutions
http://code.google.com/p/sympy/issues/detail?id=1234
oops -- 0 is excluded from the solution since log is undefined there.
--
You received this message because this project is configured to send all
issue
Comment #2 on issue 3341 by smi...@gmail.com: powsimp(4*2**n) should give
2**(n + 2)
http://code.google.com/p/sympy/issues/detail?id=3341
https://github.com/sympy/sympy/pull/1929
powsimp(4*2**n)
2**(n + 2)
powsimp(16*2**m*8**n)
2**(m + 3*n + 4)
--
You received this message because this
25 matches
Mail list logo
