This release is a pre-release and may not be stable for production use.
Featureform Python Client
Overview
Featureform’s Python client is a SDK for defining, managing and serving resources (e.g. infrastructure providers, data sources, transformations, etc.). At a high level, the API is divided into two parts:
- Registration: register data stores (e.g. PostgreSQL), data sources (e.g. tables or CSV files) as resources or get and/or list previously registered resources
- Serving: retrieve training sets and features for offline training or online inference
Requirements
- Python 3.9-3.12
Setting Up Your Local Development Environment
Step 1: Install gRPC and Protocol Buffer Tooling
See grpc.io for instructions on installing the protocol buffer compiler for your OS and language-specific plugins for Golang (NOTE: the Golang dependencies can also be installed via Homebrew.)
Step 2: Install uv and Sync Dependencies
Install uv if you haven't already. Then sync the project dependencies:
> uv sync --group dev
This creates a virtual environment and installs all required dependencies, including the featureform client in editable mode.
Step 3: Compile API Protocol Buffers and Python Stub
The shell script gen_grpc.sh has been provided for convenience. Change the file access permissions to make it executable and run it:
> chmod +x gen_grpc.sh
> ./gen_grpc.sh
Step 4: Optionally Run Client Test Suite
To ensure your changes haven’t broken the client, run the test suite with the following make target:
> make pytest
Outcome
With the steps above successfully completed, you should have the featureform CLI command accessible via uv run:
> uv run featureform -h
To further verify that your setup is complete and correct, you may optionally walk through the Quickstart tutorial. You may put the definitions.py file at the root of the project, which won’t be ignored by Git, or use a URL to a file (e.g. hosted on GitHub).
Metadata
Release files for featureform-enterprise 0.22.11rc0
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 |
|---|---|---|---|---|
| featureform_enterprise-0.22.11rc0.tar.gz | 247.4 kB | Without provenance | Details for featureform_enterprise-0.22.11rc0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| featureform_enterprise-0.22.11rc0-py3-none-any.whl | Python 3 | none | any | Details for featureform_enterprise-0.22.11rc0-py3-none-any.whl |
Total release size: 534.7 kB
Release files / featureform_enterprise-0.22.11rc0.tar.gz
| Download URL | featureform_enterprise-0.22.11rc0.tar.gz |
|---|---|
| Size | 247.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7531a48d357d6cf7540b6a3dcdc031c5b719638e9fccfca0b6d3001d925c0f7d
|
|
BLAKE2b-256 checksum How to use checksums |
b80c7045223e3753e8ac8ae83840e9014761e8dddd9430500641d6a07094185e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
Release files / featureform_enterprise-0.22.11rc0-py3-none-any.whl
| Download URL | featureform_enterprise-0.22.11rc0-py3-none-any.whl |
|---|---|
| Size | 287.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7b76b996645fc62e607c949f391683ba9b1185cad98129de7723988f8b83847
|
|
BLAKE2b-256 checksum How to use checksums |
7969e52d7a25db920808ecd87f0be36886f1d4c878e7d91df16116365858ece7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
Security for featureform-enterprise 0.22.11rc0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.