On Thu, Jun 3, 2010 at 11:04 AM, leif <not.rea...@online.de> wrote: >> > Does not really address my question. Think of a single file, what's >> > the price/latency of importing sage.all to resolve not fully qualified >> > targets (perhaps just a single one)? >> >> If you look at my new patch on trac I don't import sage.all though I search >> into it. > > Ok, your patch at #9128 obsoleted my question... > http://trac.sagemath.org/sage_trac/ticket/9128 > (I was just fearing importing sage.all takes a lot of time, at least > on older systems.)
As a note, the very first thing that $SAGE_LOCAL/bin/sphinx-build does is import sage.all. Importing it again within Sphinx afterwards just becomes a dictionary lookup. --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
