Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Very neat idea, questions about "opaque"/output in repo #3

Open
daverosoff opened this issue Mar 9, 2018 · 0 comments
Open

Very neat idea, questions about "opaque"/output in repo #3

daverosoff opened this issue Mar 9, 2018 · 0 comments

Comments

@daverosoff
Copy link

Rob—this is a nice looking project. It's another step toward what I have dreamed of since Alex J. once whispered the phrase "Beezer code" to me, an open source course that can emerge fully formed, like Minerva from the brow of Jove. I have a question: do you think there is any way to make the build truly idempotent? It seems like the .pdf and .sagews files—but not the .ipynb—will change with every build (something you avoided for HTML via --stringparam debug.datedfiles no. Feel free to respond via email if you prefer; I started an issue thinking other users might have the same question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant