See also CONTRIBUTE.md and ARCHITECTURE.md

Development is setup for local native and containerized Python coding & testing, and with automatic GitHub Actions for CI + CD. The server tests are like the local ones, except against a wider test matrix of environments.

cd docker && docker-compose build && docker-compose up -d

Containerized call to pytest for CPU + GPU modes:

cd docker

# cpu - pandas
./test-cpu-local.sh

# cpu - fast & targeted
WITH_LINT=0 WITH_TYPECHECK=0 WITH_BUILD=0 ./test-cpu-local.sh graphistry/tests/test_hyper_dask.py::TestHypergraphPandas::test_hyper_to_pa_mixed2

# gpu - pandas, cudf, dask, dask_cudf; test only one file
./test-gpu-local.sh graphistry/tests/test_hyper_dask.py

Connector tests (currently neo4j-only): cd docker && WITH_NEO4J=1 ./test-cpu-local.sh (optional WITH_SUDO=" ")

• Will start a local neo4j (docker) then enable+run tests against it

Automatically build via ReadTheDocs from inline definitions.

To manually build, see docs/.

You may need to add ignore rules:

• flake8: bin/lint.sh
• mypi: mypi.ini
• sphinx: docs/source/conf.py

Some databases like Neptune can be easier via cloud editing, especially within Jupyter:

git clone https://github.com/graphistry/pygraphistry.git
git checkout origin/my_branch
pip install --user -e .
git diff

and

import logging
logging.basicConfig(level=logging.DEBUG)

import graphistry
graphistry.__version__

GitHub Actions: See .github/workflows

• Use the unit tests
• use the logging module per-file

1. Merge the desired PR to master and switch to master head (git checkout master && git pull)

2. Manually update CHANGELOG.md

3. Tag the repository with a new version number. We use semantic version numbers of the form X.Y.Z.

   git tag X.Y.Z
   git push --tags

4. Confirm the publish Github Action published to pypi, or manually run it for the master branch

5. Toggle version as active at ReadTheDocs