Developer’s guide

Deepends on Python 3.5+

Required Modules

Installing with Conda uses environment yaml. Installing with Pip uses requirements text.


Running tests locally

$ pip install . --upgrade or python install
$ pytest -v

Testing Conda Deepforest build

We use the conda_recipe/meta.yaml to make sure that conda build can build the package

$ cd conda_recipe
$ conda build conda_recipe/meta.yaml -c conda-forge -c defaults

Conda staged recipe update

Update Conda recipe after every release.

Clone the Weecology staged recipes. Checkout deepforest branch update the deepforeset/meta.yaml with the new version and the sha256 values. Sha256 values are obtained from the source on PYPI download files. using the deepforest-{version-number}.tar.gz

{% set version = "fill new" %}
{% set sha256 = "fill new" %}


We are using Sphinx. and Read the Docs. for the documentation.

Update Documentation

The documetation is automatically updated for changes with in functions. However, the documentation should be updated after addition of new functions or modules.

Change to the docs directory and use sphinx-apidoc to update the doc’s source. Exclude the tests and documentation


sphinx-apidoc -f  -o ./source ../ ../tests/* ../

The source is the destination folder for the source rst files. ../ is the path to where the deepforest source code is located relative to the doc directory.

Test Documentation locally

cd  docs  # go the docs directory and install the current changes pip install ../ -U
make clean # Run
make html # Run

Do not commit the build directory after making html.