> I am not suggesting to patch the Sage library when installing your > package. You can put the interface in a separate Cython module which is > built by the usual Python/Cython setup.py magic and installed in the > system python module directory. Then people will be able to import your > module from the Sage command line as usual.
The python interface **uses** the sage library (matrices, modules, polynomials, term orders, etc. etc. etc.). It does not make sense outside of sage. It is a binding between sage and my piece of C-code. I actrually followed the same pattern I found there : http://trac.sagemath.org/sage_trac/ticket/418 > I don't think there is a well established procedure for this. There is > code in the Sage library that depends on optional packages. This works > just like you described. modules_list.py already includes some examples. > In this case, all doctests will need to be marked optional. Strictly speaking, they don't, because the code is not even considered if the spkg is not there. > I can see the benefits of having the wrappers "included in Sage" from a > reputation/review point of view. You are right, but again I followed what I thought was the right way to go (http://trac.sagemath.org/sage_trac/ticket/418). I certainly agree that it is a bit weird to have a lot of "inactive" code on everyone's installation. Again, what should I do :) ? Charles -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
