An example spkg could be included as a test the same way that examples in documentation are now used as a test, so there need not be an issue of the example not working. Indeed, if it is required that the documentation is updated in tandem with the example spkg, then the documentation will also be up to date.
Being the one chosen spkg would be quite a burden on that spkg, since then it cannot be allowed to become too complicated. If upstream adds complicated functionality, or if the spkg is no longer needed in Sage, then a different spkg will have to be chosen, which wastes work. I already think the Frobby spkg is too complicatedm for this purpose due to its C++ interface, since while Cython can be used with C++, the two still make an uneasy couple. Still, if it is going to be an actual spkg, then I'd propose to use Cliquer, solving both problems in this thread. Its interface is simple, it has been static over time and the code is small. Cheers Bjarke --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
