On Mon, Aug 13, 2012 at 9:24 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > On Monday, August 13, 2012 11:36:33 AM UTC-4, Robert Bradshaw wrote: >> >> Shouldn't everything needed by the sage notebook (already) be in >> sagenb.* anyways? > > > Yes, but thats not what I mean. For example, right now we import > sage.graphs.graph_editor upon startup. And the graph editor imports the sage > notebook. If the dependencies of the sage notebook were not in sys.path by > default then this wouldn't have been possible to start with.
Yeah, the import graph is pure spaghetti... I am all for making tests that certain modules are *not* imported at sage startup time which can help with more than just the notebook. This seems more explicit and simpler than installing things in different locations. - Robert -- -- 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
