On Wed, 10 Dec 2008 at 04:40AM -0800, William Stein wrote: > Note that you could also submit a patch to Sage with the code you're > doctesting. I did that with all the tests from both of the books I > published, and I encourage you and many others to do the same with the > code from your article. The code would go in a file > > devel/sage/sage/tests/ > > like the file devel/sage/sage/tests/book_stein_modform.py > > In fact, I could imagine having dozens of files in that directory, and > when doctests break there, we could notify the authors before > releasing the version of Sage that breaks their doctests for feedback > -- then they could update their papers or Sage.
I like that idea, and I do plan on getting some of this code into the main Sage library -- but for now, I just want to test some functions. I'll think about submitting my code to that tests/ directory, though. > Here's a question for you -- is there a way to embed a block of text > in an extractable way inside a pdf, etc.? If so, I think we could > easily change the notebook so ".pdf" is one of the formats for > uploading a sage worksheet. Then you could somehow embed the > worksheet itself in the pdf. Then tell readers of the pdf -- "hey, > just upload this pdf you're reading right now to any sage notebook > server, and you're good to go!" This should be possible, though it may be really hard. Or, maybe, not so hard: http://tug.ctan.org/cgi-bin/ctanPackageInformation.py?id=attachfile There's also attachfile2 and embedfile on CTAN. I agree that the coolest thing would be to just upload the PDF and have the notebook extract the code, but at any rate, we should be able to nicely include code... Dan -- --- Dan Drake <[EMAIL PROTECTED]> ----- KAIST Department of Mathematical Sciences ------- http://mathsci.kaist.ac.kr/~drake
signature.asc
Description: Digital signature
