GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — ipython/docs at main · ipython/ipython

Expand file tree

/

docs

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

docs

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
man
man
 
 
source
source
 
 
sphinxext
sphinxext
 
 
Makefile
Makefile
 
 
README.rst
README.rst
 
 
autogen_api.py
autogen_api.py
 
 
autogen_config.py
autogen_config.py
 
 
autogen_magics.py
autogen_magics.py
 
 
autogen_shortcuts.py
autogen_shortcuts.py
 
 
make.cmd
make.cmd
 
 
modernization_triage_2026-07.md
modernization_triage_2026-07.md
 
 
requirements.txt
requirements.txt
 
 

README.rst

Outline

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 documentation must be built using Python 3.

In addition to installing the development version, the following tools are needed to build the documentation:

  • sphinx
  • sphinx_rtd_theme
  • docrepr

In a conda environment, or a Python 3 venv, you should be able to run:

cd ipython
pip install -U -r docs/requirements.txt

Build Commands

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 rendering of the API documentation. This build target skips that.

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

To save time, the make targets above only process the files that have been changed since the previous docs build. To remove the previous docs build you can use make clean. You can also combine clean with other make commands; for example, make clean html will do a complete rebuild of the docs.

Continuous Integration

Documentation builds are included in the GitHub Actions continuous integration process (see .github/workflows/docs.yml), and the documentation is built on ReadTheDocs for every pull request, so you can preview the rendered result from the pull request's checks.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.