Rob Beezer wrote:
<SNIP> One solution might be to have entire books in the Sage distribution (in a source format that is not too large) and under revision control. Anyone could edit the code examples in response to patches, and the changes could be used by the author to update their canonical version. Perhaps this could all be accomplished in the spkg format, similar to making changes for upstream maintainers (along with scripts for generating books from source into different formats, such as web pages or PDF). I am not familiar enough with the technical mechanics of an spkg to be sure if this would be workable. Any informed opinions?
Currently, those tests are part of the Sage library, and the policy is that spkgs are not allowed to modify it.
We could probably move them to (e.g.) $SAGE_SHARE/doc/... though, and change doctesting (and docbuilding?) accordingly.
-leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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 http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
