Skip to content

vespa-engine/pyvespa

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Feb 28, 2025
3c8d7d3 · Feb 28, 2025
Feb 28, 2025
Aug 13, 2024
Feb 25, 2025
Feb 27, 2025
Feb 27, 2025
Nov 18, 2024
Feb 5, 2025
Apr 9, 2024
Aug 16, 2024
Aug 2, 2024
Feb 19, 2025
Oct 21, 2021
May 9, 2024
Sep 5, 2024
Oct 1, 2024
Oct 1, 2024
Oct 1, 2024
Aug 13, 2024
Aug 13, 2024
Jan 30, 2025
Jun 21, 2024
Aug 29, 2023
Jul 21, 2023
Aug 12, 2024
May 22, 2023
Jan 30, 2025

Repository files navigation

pyvespa

#Vespa

Documentation Status

GitHub Release PyPI - Version PyPI - Downloads

pyvespa site / documentation

Vespa is the scalable open-sourced serving engine that enables users to store, compute and rank big data at user serving time. pyvespa provides a python API to Vespa. It allows users to create, modify, deploy and interact with running Vespa instances. The main goal of the library is to allow for faster prototyping and get familiar with Vespa features.

vespacli

This repo also contains the python wrapper for the Vespa CLI. See README.

License

Code licensed under the Apache 2.0 license. See LICENSE for terms.

Development environment

To install editable version of the library with dev dependencies, run the following command from the root directory of the repository:

pip install -e ".[dev]"

Note that this will enforce linting and formatting with Ruff, which also will be triggered by a pre-commit-hook.

This means that you may get an error message when trying to commit changes if the code does not pass the linting and formatting checks. The errors are detailed in the output, and you can optionally run manually with ruff CLI-tool.

Releases

Find releases and release notes on GitHub.

Release details

The release flow is semi-automated, but involves a few manual steps.

  1. Create a new release from github.com/vespa-engine/pyvespa/releases/new.
  2. Make sure to tag the release with the version number, e.g., v0.41.0.
  3. This tag will trigger a github action that will publish the package to PyPI.
  4. A PR will also be automatically created to update the affected files with the new version. This PR should be merged to keep the version updated in the repository.

This workflow can also be dispatched manually, but note that steps 3 and 4 will ONLY be triggered by a release.