Ondrej Certik wrote:
> 2008/7/9 William Stein <[EMAIL PROTECTED]>:
>>>> Thanks for doing all this!  See Sage integrates into your
>>>> environment after all :-).
>>> Yes and it made me pretty excited!! Only it's 4x slower than sympy:
>> Is that "4 x" all Sage startup time, i.e., the time to do
>> "from sage.all import *"?
> 
> Yes. I work in a way that I edit a python file and the run it in
> python. So if the packages takes 2s to import, I need to wait for 2s
> everytime I edit
> a file and test it.

Sounds like what you'd want is more about supporting your workflow 
pattern than better startup times as such? I.e. something like a sage 
command-line program that would connect with a sage server and run your 
command could work. Psuedo-code:

$ sage -server
$ sage -client s.py

I.e; a "command-line notebook runner", where you keep your "notebooks" 
in Python text files, and the SAGE process stays resident. Not sure if 
something like that exists already -- just saying that I think focusing 
too hard on the startup time of the SAGE process might be the wrong way 
to go about this.

(Disclaimer: I'm only a lurker here and don't really have a clue.)

-- 
Dag Sverre

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to