##// END OF EJS Templates
Improves detection of whether tab-completion is in a string and supresses Jedi....
Improves detection of whether tab-completion is in a string and supresses Jedi. Refs #10926 and #11530 Jedi results swamp file_matches and dict_key_matches in tab-completion, which is a real nuisance. The logic in the jedi completor tried to catch cases where it was "in a string", but that logic only looked at the previous character, and was a little fragile, breaking in lots of cases such as: './<tab> "mypath/<tab> etc. This seems a bit more robust in that it searchs for the first token in the current parser tree and checks if its value starts with ' or ". This detection of "in a string" then turns of jedi and returns some sanity to the set of matches.
Coon, Ethan T -
r25487:fb0abc20
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 ...
environment.yml 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 documentation must be built using Python 3.

In additions to :ref:`devinstall`, 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 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.

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 or make clean pdf will do a complete build of the pdf.

Continuous Integration

Documentation builds are included in the Travis-CI continuous integration process, so you can see the results of the docs build for any pull request at https://travis-ci.org/ipython/ipython/pull_requests.