Bailo Python Client
A lightweight, Python API wrapper for Bailo, providing streamlined programmatic access to its core functionality - designed for Data Scientists, ML Engineers, and Developers who need to integrate Bailo capabilities directly into their workflows.
Table of Contents
Quickstart
Requires: a Python version as declared by
requires-pythonand the classifiers in pyproject.toml (also shown on PyPI)
Installation
pip install bailo
Optional: enable integration with MLFlow for advanced model tracking:
pip install bailo[mlflow]
Basic Usage
from bailo import Client, Model
# Connect to Bailo server
client = Client("http://localhost:8080")
# Create a model
yolo = Model.create(client=client, name="YoloV4", description="You only look once!")
# Populate datacard using a predefined schema
yolo.card_from_schema("minimal-general-v10")
# Create a new release
my_release = yolo.create_release(version="0.1.0", notes="Beta")
# Upload a binary file to the release
with open("yolo.onnx") as f:
my_release.upload("yolo", f)
Core Features
- Upload and download model binaries
- Manage Models & Releases
- Handle Datacards & Schemas
- Manage Schemas
- Process Access Requests
Note: Certain collaborative actions (approvals, review threads, etc.) are best handled via the Bailo web interface.
Documentation
Full Python client documentation: Bailo Python Docs.
Building locally
Refer to backend/docs/README.md for local build steps.
Development
The following steps are only required for users who wish to extend or develop the Bailo Python client locally.
Requires: uv. uv installs and uses the Python version in
.python-versionby default. Any supported version can be used with--python.
Python Setup
From within the lib/python directory:
uv sync --extra mlflow --group test
This creates a .venv and installs the pinned dependencies from uv.lock. Prefix commands with
uv run to use it, or activate it with source .venv/bin/activate.
Dependency Management
pyproject.toml declares minimum versions only (>=, no upper caps), as these are what pip install bailo users
resolve against. uv.lock pins the exact versions used in development and CI. Dependabot only raises PRs for security
advisories. Routine upgrades are manual with uv lock --upgrade-package <name>, and the ruff version comes from
.pre-commit-config.yaml.
The python_test_lowest CI job runs the tests against those minimum versions on Python 3.10. If it fails, reproduce it
locally without touching uv.lock or .venv:
uv run --python 3.10 --resolution lowest-direct --isolated --extra mlflow --group test pytest
Then raise the failing floor in pyproject.toml to the oldest version that passes, re-run the command above, and
finish with uv lock.
Running Tests
To run the unit tests:
uv run pytest
To run the integration tests (requires Bailo running on https://localhost:8080):
uv run pytest -m integration
To run the mlflow integration tests (requires Bailo running on https://localhost:8080 and mlflow running on https://localhost:5050 e.g. via docker):
docker run -p 5050:5000 \
"ghcr.io/mlflow/mlflow:v$(uv pip show mlflow-skinny | awk '/Version:/ {print $2}')" \
mlflow server --host 0.0.0.0 --port 5000
uv run pytest -m mlflow
Metadata
Release files for bailo 3.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bailo-3.12.0.tar.gz | 32.3 kB | With provenance | Details for bailo-3.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bailo-3.12.0-py3-none-any.whl | Python 3 | none | any | Details for bailo-3.12.0-py3-none-any.whl |
Total release size: 69.6 kB
Release files / bailo-3.12.0.tar.gz
| Download URL | bailo-3.12.0.tar.gz |
|---|---|
| Size | 32.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1134a8f1f8035ae4379c9a26eca56ae2b8e46b42d9781cdda7f35c263d1456c
|
|
BLAKE2b-256 checksum How to use checksums |
2abfee9c0e6cdb05c7656bf9e2438030f81ec5a53d8dce0ba33dd2d252e03190
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / bailo-3.12.0-py3-none-any.whl
| Download URL | bailo-3.12.0-py3-none-any.whl |
|---|---|
| Size | 37.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60f3644eebb1df450582a67ed8ef0e74a5c945a351a96b63fe6b53c724329ff7
|
|
BLAKE2b-256 checksum How to use checksums |
2fc960b0435a4a8b3c28a2bdda7e9ebf7230b551ebf03e7f2efc673dd02d377d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for bailo 3.12.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bailo-3.12.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.