Volker Braun <vbraun.n...@gmail.com> writes: > 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.
We already maintain a Python installation separate from the system Python. Now you want to keep some of our python packages in yet another location? Is that really necessary? I don't see why in order to make certain modules not import on startup they must be physically moved elsewhere. Or is the problem that Python is taking too long to even scan the site-packages directory? -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- -- 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
