NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #5568 most downloaded on PyPI
Python API for vespa.ai
Latest stable
1.2.10
Last release 23 days ago
30 Oct 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
6 years old
102 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
app.collect_training_data_point and app.collect_training_data will be deprecated in future releases and should be replaced by app.collect_vespa_featur…
app.collect_training_data_point (https://github.com/vespa-engine/pyvespa/pull/345)app.collect_vespa_features and app.store_vespa_features that use app.query_batch to speedup Vespa feature collection. (https://github.com/vespa-engine/pyvespa/pull/347)app.collect_training_data_point and app.collect_training_data will be deprecated in future releases and should be replaced by app.collect_vespa_features and app.store_vespa_features.Fix bug (https://github.com/vespa-engine/pyvespa/issues/341) that requires users to install ml packages when importing the application module.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Improve output on deployment failure
namespace argument to document operations (https://github.com/vespa-engine/pyvespa/pull/337)recall argument (https://github.com/vespa-engine/pyvespa/pull/338)vespa.experimental.ranking module (https://github.com/vespa-engine/pyvespa/pull/336)Enable Docker deployment via a POST request
Enable Docker deployment without disk_folder specification through a zip file.
disk_folder specification through a zip file. (https://github.com/vespa-engine/pyvespa/pull/313, https://github.com/vespa-engine/pyvespa/pull/315)Use latest transformer library and pipeline class.
transformer library and pipeline class. (https://github.com/vespa-engine/pyvespa/pull/254)container_image when creating a VespaDocker instance.app.query_batch: Add method to send queries in batch
app.query_batch: Add method to send queries in batch (https://github.com/vespa-engine/pyvespa/pull/244)Add retry strategy to delete_data, get_data and update_data
delete_data, get_data and update_data (https://github.com/vespa-engine/pyvespa/pull/222)disk_folder defaults to the current working directory for both Docker and Cloud deployment (https://github.com/vespa-engine/pyvespa/pull/225)Infer schema name whenever possible for batch document operations
Removes vespa.package module dependency on the vespa.ml module. The main goal is to avoid installing vespa.ml specific dependencies through pip instal
Removes vespa.package module dependency on the vespa.ml module. The main goal is to avoid installing vespa.ml specific dependencies through pip install pyvespa[ml] unless the user explicitly wants to use vespa.ml classes.
Use tasks instead of models as argument name for ModelServer to align with the fact this argument takes instances of type TextTask.
tasks instead of models as argument name for ModelServer to align with the fact this argument takes instances of type TextTask.model_id instead of model_name to identify a model since model_id is what we use when defining a Task.Introduce stateless model evaluation with SequenceClassification task.
Introduce stateless model evaluation with SequenceClassification task.
ApplicationPackage to allow for simpler configurations, e.g. no schema.ModelServer, which is a simplified ApplicationPackage focused on stateless model evaluation.ApplicationPackage is now included on the Vespa instance when deploying apps with pyvespa.
app.predict.Vespa now has get_model_endpoint and predict to use for stateless model evaluation mode.VespaDocker and VespaCloud now work with ModelServer deployment to deploy stateless model evaluation apps.SequenceClassification task that inherits from the base class TextTask.VespaDocker and VespaCloud are now only available via the vespa.deployment module.
VespaDocker and VespaCloud are now only available via the vespa.deployment module.
v 0.8.1 still works with vespa.package.VespaDocker and vespa.package.VespaCloud but it will issue a deprecation warning informing users to use vespa.d…
VespaDocker and VespaCloud will move to the deployment module
vespa.package.VespaDocker and vespa.package.VespaCloud but it will issue a deprecation warning informing users to use vespa.deployment.VespaDocker and vespa.deployment.VespaCloud instead.vespa.package.VespaDocker and vespa.package.VespaCloud and users must use vespa.deployment.VespaDocker and vespa.deployment.VespaCloudNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.