On 04/22/2013 09:57 AM, Felix Salfelder wrote:
do you see disadvantages in treating sage parts as modules?
It doesn't even make sense to treat them as modules, since they are not
independent. libcsage means nothing without the Sage Python library, the
Sage Python library requires libcsage and the scripts make no sense
without Sage.
maybe it doesnt matter much, whether c_lib and scripts are in the same
module or not, for distribution purposes it makes sense to have
python-sage and sagenb seperated.
sagenb is a separate project, at least on paper. Currently Sage doesn't
work without sagenb, but one could argue that's a bug.
--
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 http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
