Investigate how to release packages whose source contains ipynb files

[yuvipanda]

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)

[yuvipanda]

If we really get this going we could maybe go all meta and write ipynb in ipynb :D

[Carreau]

So there are various ways to do that:

1. 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.

2. Require ipynb, an one .py files that "register" this particular packages as a prefix for which the import hook should work.

[yuvipanda]

Yeah, I prefer 1 far more than 2. I suppose we just need a way to do pre-processing of files?

[Carreau]

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.

[yuvipanda]

This is done now, we have a setup_packages() implementation.