Thanks for the help so far. I've been able to make some minor changes
to the code
and checked the behaviour. I'm still a bit stuck on how it all ties
together. I have added
a new routine to the C++ code, but so far I've been unable to trace
how the existing
code is invoked from the Python code.
Hi,
I got the error in subject while trying the new ECM().one_curve() command
in sage-2.9. The problem might be due to the fact that I perform thousands of
calls to ECM().one_curve(), and maybe pexpect does not correctly frees pty
devices.
The problem can be reproduced with:
$ sage
I am working today and tomorrow on fixing all your typos and
possibly adding a few more examples to the tutorial.
Thanks very much for your reports.
++
On Dec 17, 2007 12:23 PM, bill purvis [EMAIL PROTECTED] wrote:
Hi,
I'm looking at the Sage Tutorial, file
When I build sage-2.9.1.1 from source on the architectures
of interest to me, I get an error when building
mpfi-1.3.4-cvs20071125.p2
gcc -fPIC -o test_mpfi test_mpfi.o ../src/.libs/libmpfi.a
/home/kate/sage/sage-2.9.1.1-x86_64-Linux/local/lib/libmpfr.a -lgmp
On Dec 27, 4:39 pm, Kate Minola [EMAIL PROTECTED] wrote:
Hi Kate,
When I build sage-2.9.1.1 from source on the architectures
of interest to me, I get an error when building
mpfi-1.3.4-cvs20071125.p2
gcc -fPIC -o test_mpfi test_mpfi.o ../src/.libs/libmpfi.a
I'm having problems doing symbolic computations in Sage. Calls to
rational_simplify() seem to take about .2 seconds each. Working
directly in Maxima is about 100 times faster. Mathematica is
something like 500 times faster.
In Sage, where does the time go? Is there something I can do right
Hello,
The reason why the symbolic stuff in Sage is slow is that it uses a
psuedo-tty interface to talk to Maxima. There is a lot of overhead
with this due to waiting, synchronization, parsing the string output,
etc. One way to get the symbolic stuff to be faster is to make using
Sympy since
On Dec 27, 9:57 pm, Mike Hansen [EMAIL PROTECTED] wrote:
Hello,
The reason why the symbolic stuff in Sage is slow is that it uses a
psuedo-tty interface to talk to Maxima. There is a lot of overhead
with this due to waiting, synchronization, parsing the string output,
etc. One way to
Hi:
Suppose you follow the instructions in the programming
manual to edit one of the latex doc files, such as prog,tex,
const.tex, tut.tex, etc.
http://www.sagemath.org/doc/html/prog/node31.html
Roughly, the steps are
sage: hg_doc.pull()
(edit the file, say devel/doc/prog.tex)
sage:
