Yippieh, that's what I really love about Sage: you'll never walk alone! What about the following idea: let's create
sage.libs.playground and, say, Cython (sub-)modules sage.libs.playground.exampleclib sage.libs.playground.examplecpplib which are amply documented despite their names, but in a setting that does encourage one to add some sage.libs.playground.mylib and step-by-step (or whatever helpful) instructions how to do this as easy as 1-2-3. I now admit that already twice, I had created an "exampleclib.spkg" together with complete Cython interface code. But I made (twice ...) the mistake to put the latter under .../python/site-packages/... and I think that in the end, this offended the referee(s) to such a degree, that these attempts had to fail. (I also admit that I had made almost any other mistake, too, e.g. not only creating a patch-bomb spkg, but also uploading it to trac, introducing far more than needed complexity, etc.pp. If you wish, have a look at the history of the "needs work" trac ticket #4857 ...) We (Michael Abshoff and me) could reach agreement on how the "Example C Library spkg" shall look like, so this is almost 100% re-usable. (Although e.g. Frobby is much more complete, especially concerning the/ an optional test suite.) The Cython interface code pre-dates the Sage ReST-/Sphinxification, so there might be some work to do here. (The move *into* the Sage Library is actually very easy, now that the distinct "module_list.py" came into existence.) Both the Frobby-Cython interface to be created, and the Cliquer.spkg and Cliquer-Cython interfaces to come into existence, may serve as first "real-life" tests to round off the edges of this new "Sage playground" . And of course, I'm happy not only to answer a question or two, but to try to improve the documentation in such a way, that others will find these answers, too, should they have the same questions. Or do you have a better idea/name for the above than "sage.libs.playground"? Cheers, gsw P.S.: William, to answer that one of your remarks: IMHO, the best "current" example C(CPP) library / Cython interface code in Sage is the "hypellfrob" one from David Harvey, but it's neither under "sage.libs" (the content of which is quite, ahem, inhomogeneous), nor is the non-Cython part of it in spkg format ... --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
