The README section Collaborating on notebooks with Git
nicely describes how to create the .ipynb files for .py notebooks under version control. Thank you for that documentation. The actual process is a little tedious if you have several notebooks and the .py notebook files are somewhat buried.
For projects with configuration files that shows where .ipynb notebooks should be, would it be reasonable to have a shortcut to generate any that are missing? One possibility: execute jupytext --sync with no additional arguments in a project with a jupytext configuration file.
Thanks @itcarroll for documenting this. Sorry I did not comment earlier. You might also want to use the globstar ** operator for accessing multiple depths at once, see here. Cheers
The README section Collaborating on notebooks with Git nicely describes how to create the
.ipynb
files for.py
notebooks under version control. Thank you for that documentation. The actual process is a little tedious if you have several notebooks and the.py
notebook files are somewhat buried.For projects with configuration files that shows where
.ipynb
notebooks should be, would it be reasonable to have a shortcut to generate any that are missing? One possibility: executejupytext --sync
with no additional arguments in a project with a jupytext configuration file.