Hi! At https://trac.sagemath.org/ticket/18514 I am in the process of upgrading my old-style group cohomology spkg to a more modularised new-style spkg.
I've put it on "needs info", and perhaps some of you can give me the information that I need to finish the upgrade. The branch at #18514 is based on the latest MeatAxe spkg (whereas my old-style spkg *included* a copy of an outdated MeatAxe source). It uses an autotoolised version of code of David Green (the old-style spkg used a hand-knitted Makefile). And because I found development easier in that way, all Cython and Python code currently is put into the Sage src tree, as OptionalExtension. I was told here that I should remove my code from the src tree (I agree) and turn it into a pip-installable module. But how? I need help for creating a correct setup.py. Also, I'd like to build documentation. Sébastien has pointed me to https://github.com/seblabbe/slabbe as an example of code that uses Sage's doc formatting, and people here have pointed me to google docs. However, my question is: Is the Makefile that I find in https://github.com/seblabbe/slabbe/tree/master/docs hand made? Or is there something similar to autotools that helps me creating such a makefile? And is it really needed to have a lengthy (hand written?) conf.py, when all I want is to do whatever Sage does for building its docs? I guess my question would be similar for google docs. So, basically what I need is help to rip code off Sage's src tree and move it into an external package, such that it still works and builds docs. Best regards, 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.
