-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Tutorials infrastructure: switch to text-based notebook workflow #59
Conversation
Hello @alexdesiqueira! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-12-10 07:09:55 UTC |
Alright, I think that's it as a starting point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexdesiqueira in addition to the minor comments below, why are the existing tutorials not migrated here? I would prefer that ongoing PRs only add content rather than removing it! 😂
.github/workflows/deploy.yml
Outdated
- name: GitHub Pages action | ||
if: github.repository == 'scikit-image/skimage-tutorials' && github.ref == 'refs/heads/main' && github.event_name == 'push' | ||
uses: peaceiris/actions-gh-pages@v3.6.1 | ||
with: | ||
github_token: ${{ secrets.GITHUB_TOKEN }} | ||
publish_dir: ./_build/html | ||
publish_dir: ./website/_build/html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this move? I don't love it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I felt it'd make things more organized. I don't mind, though. Would you like me to leave it as it was?
@jni* We're not removing anything yet! 😂 If I convert everything now, this PR will be huge; the idea here was only to add the infrastructure — the tutorial(s) presented here are examples 🙂 |
Thank you @stefanv! |
Something isn't right with the caching: it rebuilds all notebooks on each make. |
The Makefile is definitely not right... refers to a |
@stefanv thanks; gonna check that. |
I will push up a patch, then you can work on top of that. |
Actually, the whole thing is completely broken :) |
😂 Sorry about that. |
bb2a1e8
to
560d599
Compare
560d599
to
d4325e7
Compare
OK, I pushed up a new Makefile and switched to using jupytext to render directly. Jupytext correctly passes through failing cells with the Process now is:
There's no caching, but make will not rebuild a notebook unless it has changed. I.e., if a .md source file is modified, the notebook is re-rendered and re-executed. There will be failures on CI. These are real failures that need to be fixed. |
3ca72c8
to
ef683cc
Compare
Adding my two cents from afar... Though the build system is a departure from the jupyter-book or pure-sphinx workflows, it LGTM and shouldn't make a difference to tutorial authors one way or the other once everything is working. From trying it out, there are two main features that you get from the sphinx/jb workflows that are missing here:
|
@rossbar do you want to update the build system to use the Sphinx workflow? Fine with me, as long as we have the ability to error on failed build for CI purposes. |
I am a bit surprised at the rebuilds. That's the whole point of make, but I observe the same thing. |
Sure, I'm happy to do so, if for no other reason than to provide a point of comparison.
Yeah this is a bit of a sore point: I do this with the |
Changes the workflow to use a text-based format for Jupyter notebooks and sphinx+myst for running and testing them, continuing changes added by @jni.
Kindly stolen from @rossbar's numpy-tutorials.