##// END OF EJS Templates
run_cell returns an ExecutionResult instance...
run_cell returns an ExecutionResult instance gh-7256 asked for a boolean return value from run_cell() for whether code ran successfully. I discussed this with Min, who suggested that given the complexity of run_cell, it should return a result object that can store different pieces of information about what happened. This currently stores `execution_count`, `error_before_exec` (i.e. errors transforming, parsing or compiling the code), `error_in_exec` and `result`. It calculates `success` as a boolean that's true if neither of the error fields are set. Closes gh-7256
Thomas Kluyver -
r19630:0e76a046
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 ...
jsdoc_config.json Loading ...
jsdoc_plugin.js Loading ...
make.cmd Loading ...

IPython Documentation

This directory contains the majority of the documentation for IPython.

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.