I would propose that we go one step further: * Install all notebook dependencies into a separate directory * only import notebook() from the sagenb on startup * The notebook() function adds notebook dependencies to sys.path before importing its prerequisites
This would force the notebook to be modular and separate from the sage library. You would be able to run the sage commandline without openssl, for example. On Sunday, August 12, 2012 6:57:43 PM UTC-4, Mike Hansen wrote: > > On Sun, Aug 12, 2012 at 12:51 PM, Volker Braun > <vbrau...@gmail.com<javascript:>> > wrote: > > For comparison, here is sage-5.1.rc1. It looks like the notebook update > > pulled in two slow modules: flaskext.babel and pytz. And we now have a > > longer sys.path (from 26 to 39 entries), which makes module loading > overall > > slower. Especially since the filesystem is 4x slower than on my laptop > for > > some reason. > > One easy improvement is to use pip instead of setuptools so that > things aren't added to sys.path when installing modules -- they're > just put directly in site-packages. We should also be able to > restructure notebook imports so as not to have to pull in > flaskext.babel and pytz. > > --Mike > -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
