-
Notifications
You must be signed in to change notification settings - Fork 44
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
IPython versions of chapters #8
Comments
Maybe it's obvious but just to note - No idea how to do the conversion in the CI, you have much more experience with that :-) In any case, once we have the |
For reference: mwouts/jupytext#202 (comment) can go to .py and quarto convert can go to .ipynb. See quarto-dev/quarto-cli#389 also. |
This is now done, as can be seen in this commit that was pushed on actions: 4e7d8c9 Question is: where to put the content? I guess the code will be well placed in a |
Sounds great to me, there could be an |
I'm seeing that there are |
Agreed. Can be changed in the yml GitHub workflow file. |
Same with the .Py files which can go in code or code/chapters directory right? Put there as a proof of concept. |
Problem: the data folder doesn't exist in the ipynb or python directories. Proposed solution: download and unzip a folder containing the input data if it doesn't exist, e.g. using solutions mentioned here: https://stackoverflow.com/questions/9419162/download-returned-zip-file-from-url |
Closed in fe5c344 and other commits above. Any follow-up comments on how we've done this and where to keep the files, welcome! |
quarto convert test.qmd
The text was updated successfully, but these errors were encountered: