On Sat Jun 06, 2020 at 08:10:37AM +0200, Bjorn Ketelaars wrote: > On Fri 05/06/2020 12:38, Thomas Frohwein wrote: > > ping > > > > On Sat, May 23, 2020 at 03:33:48PM -0600, Thomas Frohwein wrote: > > > Hi, > > > > > > Jupyter Notebooks are a mess to version control, as they contain > > > encoded output data, like the images of graphs. > > > > > > The best way to version control that I have found is ipynb-py-convert > > > which converts the notebooks into .py files that only include input, as > > > well as comments '# %%' to indicate the cell separators. Markdown cells > > > are converted to python multiline strings. > > > > > > This is a very straightforward port from pypi.org. The syntax is: > > > > > > $ ipynb-py-convert [input] [output] > > > > > > I've tested it with a Jupyter Notebook that I'm working on and > > > successfully converted it to .py and back, with no issues in the > > > resulting .ipynb. > > > > > > ok? > > I think it is nice to have this tool in ports. Two comments/questions: > - I'm not sure that www is the right category, is devel not more > appropriate?
IMHO devel is already too full. > - Maybe add HOMEPAGE=https://github.com/kiwi0fruit/ipynb-py-convert to > Makefile? >
