Examples

Interpolation can be performed on collections of points represented in a variety of ways:

>>> lagrange({1: 15, 2: 9, 3: 3}, 17)
4
>>> lagrange([(1, 15), (2, 9), (3, 3)], 17)
4
>>> lagrange([15, 9, 3], 17)
4
>>> lagrange(
...     {
...         1: 119182, 2: 11988467, 3: 6052427, 4: 8694701,
...         5: 9050123, 6: 3676518, 7: 558333, 8: 12198248,
...         9: 7344866, 10: 10114014, 11: 2239291, 12: 2515398
...     },
...     15485867
... )
123
>>> lagrange(
...     [
...         119182, 11988467, 6052427, 8694701, 9050123, 3676518,
...         558333, 12198248, 7344866, 10114014, 2239291, 2515398
...     ],
...     15485867
... )
123

Documentation

The documentation can be generated automatically from the source files using Sphinx:

python -m pip install ".[docs]"
cd docs
sphinx-apidoc -f -E --templatedir=_templates -o _source .. && make html

Testing and Conventions

All unit tests are executed and their coverage is measured when using pytest (see the pyproject.toml file for configuration details):

python -m pip install ".[test]"
python -m pytest

Alternatively, all unit tests are included in the module itself and can be executed using doctest:

python src/lagrange/lagrange.py -v

Style conventions are enforced using Pylint:

python -m pip install ".[lint]"
python -m pylint src/lagrange

Contributions

In order to contribute to the source code, open an issue or submit a pull request on the GitHub page for this library.

Versioning

Beginning with version 0.2.0, the version number format for this library and the changes to the library associated with version number increments conform with Semantic Versioning 2.0.0.

Publishing

This library can be published as a package on PyPI via the GitHub Actions workflow found in .github/workflows/build-publish-sign-release.yml that follows the recommendations found in the Python Packaging User Guide.

Ensure that the correct version number appears in pyproject.toml, and that any links in this README document to the Read the Docs documentation of this package (or its dependencies) have appropriate version numbers. Also ensure that the Read the Docs project for this library has an automation rule that activates and sets as the default all tagged versions.

To publish the package, create and push a tag for the version being published (replacing ?.?.? with the version number):

git tag ?.?.?
git push origin ?.?.?