Hi! On 2016-04-08, Volker Braun <vbraun.n...@gmail.com> wrote: > Automatic import of additional globals into the Sage command line should be > determined by configuration file(s) in SAGE_LOCAL/etc/sagemath (or so), not > by mokeypatching stuff in Sage. Feel free to send in a patch...
One should also mention that meanwhile we have optional Cython modules. In other words, if you have an optional spkg foo and some code that makes foo usable in Sage, then you could create an optional Cython module sage.bar that depends on foo. Consquence: - Documentation of sage.bar would be available, regardless whether foo is installed or not. A side remark on modularisation: I very much appreciate to have the full documentation available from within Sage. I wouldn't like to search the internet for documentation of things that I *could* do with Sage after installing some optional module. - The installation of the optional spkg foo would *not* alter the Sage library (which would end in chaos). Instead, "make foo" (if I recall correctly) would install the optional spkg foo and then create sage.bar. While documentation of sage.bar is always available, documentation of foo will only be available after you install it, preferably in the default location mentioned by Volker. See sage.matrix.matrix_gfpn_dense for an example (and have a look at SAGE_ROOT/src/module_list.py). It is an optional Cython module depending on the optional MeatAxe spkg. Cheers, Simon -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
