##// END OF EJS Templates
Don't require win_unicode_console on Python 3.6...
Don't require win_unicode_console on Python 3.6 It looks like the changes Drekin's win_unicode_console makes have essentially been integrated into Python 3.6, so it will use the Unicode APIs for Windows console access by default. See [PEP 528](https://www.python.org/dev/peps/pep-0528/). So we shouldn't need to load WUC on Python 3.6, and it may even have some strange interactions.
Thomas Kluyver -
r22867:190ffa3c
Show More
Name Size Modified Last Commit Author
/ docs
man
source
sphinxext
Makefile Loading ...
README.rst Loading ...
autogen_api.py Loading ...
autogen_config.py Loading ...
autogen_magics.py Loading ...
autogen_shortcuts.py Loading ...
make.cmd Loading ...
requirements.txt Loading ...

IPython Documentation

This directory contains the majority of the documentation for IPython.

Deploy docs

Documentation is automatically deployed on ReadTheDocs on every push or merged Pull requests.

Requirements

The following tools are needed to build the documentation:

  • sphinx

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

sudo apt-get install python-sphinx

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

make html - build the API and narrative documentation web pages, this is 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 pdf will compile a pdf from the documentation.

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