Encountered this issue when installing with pip install ipyext

Collecting ipyext
  Using cached https://files.pythonhosted.org/packages/1e/eb/c0ca3aec31d5cd658d3ad9fb4427e36831eba1320e5e4fa9cb7f86e33345/ipyext-0.1.0.zip
    Complete output from command python setup.py egg_info:
    !!! DON'T UPLOAD TO PyPI, DESCRIPTION IS WRONG FORMAT
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-_yZbeC/ipyext/setup.py", line 22, in <module>
        with io.open('README.md', encoding="utf-8") as f:
    IOError: [Errno 2] No such file or directory: 'README.md'

Could be fixed by including a MANIFEST.in file

What am I doing wrong? Is it a temporary issue?

pip install ipyext
Collecting ipyext
  Could not find a version that satisfies the requirement ipyext (from versions: )
No matching distribution found for ipyext


pip --version
pip 7.1.2 from /Users/sam/anaconda/lib/python3.4/site-packages (python 3.4)

(root) C:\Users\amara>conda install -c https://conda.anaconda.org/janschulz ipyext
Fetching package metadata .................
Solving package specifications: .

UnsatisfiableError: The following specifications were found to be in conflict:
  - ipyext -> python 2.7*
  - python 3.6*
Use "conda info <package>" to see the dependencies for each package.

Other than that, just loading writeandexecute.py seems to work.

R has the concept of a demo: https://stat.ethz.ch/R-manual/R-devel/library/utils/html/demo.html

It would be nice if we had a demo function, which would take a module/function and turn it into jupyter notebook cells:

from ipyext.demo import notebook_demo as demo # make it cristall clear that we only work in the notebook
import matplotlib.demo # something which isn't there yet :-)
demo(matplotlib.demo)
# shows available demos, as that's a module
demo(matplotlib.demo.gridspec)
# would add some cells below which are prefilled with examples how to use gridspec

Demo would:

• make sure that the function takes no argument
• get the source of a function and dedent it
• split the source into blocks (code + comments with ^# Text -> comments with ^#text stay as comments in the code cell)
• remove # from all comment lines
• add the blocks to the notebook (see here for an example how to do that

Only problem when using functions: we can't use %magics in demos. Not sure if there is a workaround that, maybe treat #%magic ... as code, aka s/#%/%/ before splitting into blocks?

@asmeurer

The goal if the org and this repo is to have easier admin organisation, and centralize small snippets.

Basically everyone is owner, so we can make simple bug fixes, or help users when one of us is unavaillable.

For small one file extension, we decided it was easier to have 1 repo with small file, but if you want 1 repo only for your extension, and be admin on it it's doable too.

It just much easier to point user to ipython-contrib than to remember the extension A in on github/carreau, extension B is on MinnRK, extension C is fperez_org, and have to bother the repo owner if the extension becomes unmaintained to add new contributors, people with commit rights.

So if you want to migrate your extension here, I would be happy to give you owner right, I like a few other from the org to agree too.

Is that more clear ?

It will be easier to discuss here than in 140 in Twitter.

IMO it would be good if each extension would have:

• some tests (-> setup travis, give some example how to test magics)
• a doc page (-> setup sphinx + readthedocs)

Any other requirements so that this doesn't become stale?

I will port a few extensions which I use to this repo and try to setup the build process, travis and the doc building and so on...