Hi,
I think the startup time of Sage may be starting to get out of control
again. For example, I'm concerned about some modules called
"flask_babel", "pytz" and "uuid", which seem to take a substantial
fraction of a second, and should probably be imported at runtime, not
at startup. For example, flask_babel takes 0.2 seconds to import.
It's description is: "Adds i18n/l10n support to Flask applications".
I don't see why we need that at Sage startup. It's imported by
sage/devel/sagenb/sagenb/notebook/template.py
Why is "sagenb" being imported at all on sage startup? It's because
of this in sage.all:
from sage.server.all import *
Commenting out the code from sage/all.py that imports this breaks
library interacts, of course. Anyway, I just thought I would point
this out, in case anybody wants to fix it (I don't at the moment).
Anywhere, here is the worst part fo the output of sage -startuptime:
...
27.638 36.770 250 sage.structure.element
31.930 2061.894 5 sage.all
34.867 36.348 5 pytz
39.333 39.948 2 uuid
50.933 51.200 5 pkg_resources
59.811 211.645 5 flask_babel
141.628 750.529 236 sage
Total time (sum over exclusive time): 2132.410ms
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
