On Mon, Nov 24, 2008 at 8:47 AM, Mateusz Paprocki [EMAIL PROTECTED] wrote:
On Sun, Nov 23, 2008 at 09:27:05PM +0100, Fabian Seoane wrote:
The problem with factorization code is that it requires a lot of
CPU resources, so spending time on anything else that computing,
e.g. object creation,
Fredrik Johansson wrote:
On Mon, Nov 24, 2008 at 8:47 AM, Mateusz Paprocki [EMAIL PROTECTED] wrote:
On Sun, Nov 23, 2008 at 09:27:05PM +0100, Fabian Seoane wrote:
The problem with factorization code is that it requires a lot of
CPU resources, so spending time on anything else that computing,
On Mon, Nov 24, 2008 at 1:35 AM, [EMAIL PROTECTED] wrote:
From: Fabian Seoane [EMAIL PROTECTED]
For this, a guess_solve_strategy method was added
Before of this, solve() parsed the expression searching for a polynomial
and if this parse failed, it just called tsolve.
Now the expression
Ondrej Certik wrote:
On Mon, Nov 24, 2008 at 1:35 AM, [EMAIL PROTECTED] wrote:
From: Fabian Seoane [EMAIL PROTECTED]
For this, a guess_solve_strategy method was added
Before of this, solve() parsed the expression searching for a polynomial
and if this parse failed, it just called tsolve.
From: Fabian Seoane [EMAIL PROTECTED]
For now this is just a variable sympy.SYMPY_DEBUG that has values True/False.
Values for this are set using the environment variable SYMPY_DEBUG
---
doc/src/guide.txt |9 +
sympy/__init__.py |3 +++
2 files changed, 12 insertions(+), 0
