We follow the Jupyter Contribution Workflow and the IPython Contributing Guide.
In order to test all the features of nbconvert you need to have pandoc and
TexLive installed.
In your environment pip install -e '.[all]' will be needed to be able to
run all of the tests and to test all of the features.
If you only want to run some of the tests run pip install -e '.[test]'.
NbConvert includes a substantial amount of both user and API documentation.
We use sphinx to build the API documentation.
Much of the user documentation is written in Jupyter Notebooks and converted on the fly with nbsphinx.
To build nbconvert's documentation you need to have pandoc and
TexLive installed.
If you want to build the docs you will need to install the docs dependencies in addition to
the standard dependencies. You can get all of the dependencies by running pip install -e '.[all]' and if you want only those needed to run the docs you can access them with pip install -e '.[docs]'.
Full build instructions can be found at docs/README.md.
nbconvert has adopted automatic code formatting so you shouldn't
need to worry too much about your code style.
As long as your code is valid,
the pre-commit hook should take care of how it should look.
pre-commit and its associated hooks will automatically be installed when
you run pip install -e ".[test]"
To install pre-commit manually, run the following:
pip install pre-commit
pre-commit installYou can invoke the pre-commit hook by hand at any time with:
pre-commit runwhich should run any autoformatting on your code and tell you about any errors it couldn't fix automatically. You may also install black integration into your text editor to format code automatically.
If you have already committed files before setting up the pre-commit
hook with pre-commit install, you can fix everything up using
pre-commit run --all-files. You need to make the fixing commit
yourself after that.
Some of the hooks only run on CI by default, but you can invoke them by
running with the --hook-stage manual argument.