##// END OF EJS Templates
Remove outdated info from README...
Remove outdated info from README We no longer use submodules, and a development install is now no different from how you'd do an editable install of any Python package, so there's no need for us to be documenting it explicitly.
Thomas Kluyver -
r21499:bec8d3dc
Show More
Name Size Modified Last Commit Author
/ docs
man
resources
source
sphinxext
Makefile Loading ...
README.rst Loading ...
autogen_api.py Loading ...
autogen_config.py Loading ...
autogen_magics.py Loading ...
gh-pages.py Loading ...
make.cmd Loading ...

IPython Documentation

This directory contains the majority of the documentation for IPython.

Deploy docs

Run make gh-pages, and follow instruction, that is to say: cd into gh-pages, check that everything is alright and push.

Requirements

The following tools are needed to build the documentation:

sphinx jsdoc

On Debian-based systems, you should be able to run:

sudo apt-get install python-sphinx npm
sudo npm install -g jsdoc@"<=3.3.0"

The documentation gets built using make, and comes in several flavors.

make html - build the API (both Javascript and Python) and narrative documentation web pages, this is the the default make target, so running just make is equivalent to make html.

make html_noapi - same as above, but without running the auto-generated API docs. When you are working on the narrative documentation, the most time consuming portion of the build process is the processing and rending of the API documentation. This build target skips that.

make jsapi - build Javascript auto-generated API documents.

make pdf will compile a pdf from the documentation.

You can run make help to see information on all possible make targets.