davidloeffler ha scritto: > Another alternative: if you call your file "test.sage" rather than > "test.py", and then do "sage test.sage" from the command line, it will > be run as if you had typed all the corresponding commands in a Sage > session, so you don't need the "from sage.all import *" line in > Laurent's example above. > In the case where I'm using the test.sage trick, can I still import my own modules or have access to everything ? I guess the answer is Yes, isn't ?
Other point : when I write scripts like the one I posted, the execution is quite slow, at least, it takes a while before starting. I suppose that the line from sage.all import * takes ages. Is there a way to import less ? Have a good afternoon Laurent --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
