Well, I've gone for this attempt and have ended up with two files, polytopes_grdb_backend.py that contains all my functions, and polytopes_grdb.py that just imports the functions we want to appear to the user, and then all.py imports polytopes_grdb.
The problem here is that even if I write the documentation in polytopes_grdb_backend as though they were functions in polytopes_grdb this is fine for in-sage documentation, what about for the reference documentation? If I tell Sphinx to add polytopes_grdb to the documentation, nothing will appear, as the documentation is in polytopes_grdb_backend; but if I tell it to bring up polytopes_grdb_backend then the functions are shown to the user as living there and not in polytopes_grdb as we want them to believe. Thoughts? Sam. -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
