Investigate how to release packages whose source contains ipynb files
yuvipanda opened this issue · 5 comments
Ideally these will not require the ipynb package at all at runtime. We could do some amount of pre-processing to make sure we ship .py files rather than .ipynb files, and dependency on IPython itself will depend on #6.
This totally requires us to have a solid documented understanding of how relative imports work (see #4)
If we really get this going we could maybe go all meta and write ipynb in ipynb :D
So there are various ways to do that:
-
have the "setup.py" to build a py-version of all the notebooks.
I'm going to assume that users won't modify an installed package :-)
Then it will require ipynb as install time. Though "show source" might be wrong-ish. -
Require
ipynb
, an one.py
files that "register" this particular packages as a prefix for which the import hook should work.
Yeah, I prefer 1 far more than 2. I suppose we just need a way to do pre-processing of files?
Yeah, I prefer 1 far more than 2. I suppose we just need a way to do pre-processing of files?
Should not be too hard.
This is done now, we have a setup_packages()
implementation.