Python library for trichotomous voting.
The complete documentation is available here. It includes
- installation instructions,
- a short guide for a quick start,
- a complete guide to go further,
- a reference guide to get all the details.
We are more than happy to receive help with the development of the package. If you want to contribute, here are some elements to take into account.
First, install the development dependencies by running the following command:
pip install -e ".[dev]"
You can run the unit tests with the following:
python -m unittest
The doc is generated using sphinx. We use the numpy style guide. The napoleon extension for Sphinx is used and the HTML style is defined by the Book Sphinx Theme.
To generate the doc, first move inside the docs-source
folder and run the following:
make clean
make html
This will generate the documentation locally (in the folder docs-source/build
). If you want the documentation
to also be updated when pushing, run:
make githubclean
make github
After having pushed, the documentation will be automatically deployed to the GitHub page.
Note that a large part of the documentation is done by hand (to ensure proper display and correct ordering).
This means that if you create new class of functions that should appear in the documentation, you may have
to add they yourself using to autodoc directives (take inspiration from the files in docs-source/source
).
The pipeline between GitHub and PyPI is automatised. To push a new version do the following:
- Update the
pyproject.toml
with the new version number. - Update the
trivoting/__init__.py
with the new version number. - On GitHub, create a new release tagged with the new version number (only admins can do that), on this page.
- You're done, the new version of the package is automatically pushed to PyPI after the creation of a GitHub release.
If the docs-source has been updated but the docs/
folder has not, you can build the docs via
a GitHub action here: https://github.com/COMSOC-Community/trivoting/actions/workflows/docs.yml.
Simply click "Run workflow" and the docs will be built and the built files will be pushed back to
the server.