Skip to main content

redisai-py

https://img.shields.io/github/license/RedisAI/redisai-py.svg https://badge.fury.io/py/redisai.svg https://github.com/RedisAI/redisai-py/actions/workflows/integration.yml/badge.svg https://img.shields.io/github/release/RedisAI/redisai-py.svg https://codecov.io/gh/RedisAI/redisai-py/branch/master/graph/badge.svg https://readthedocs.org/projects/redisai-py/badge/?version=latest https://img.shields.io/badge/Forum-RedisAI-blue https://img.shields.io/discord/697882427875393627?style=flat-square https://snyk.io/test/github/RedisAI/redisai-py/badge.svg?targetFile=pyproject.toml

redisai-py is the Python client for RedisAI. Checkout the documentation for API details and examples

Installation

  1. Install Redis 5.0 or above

  2. Install RedisAI

  3. Install the Python client

$ pip install redisai
  1. Install serialization-deserialization utility (optional)

$ pip install ml2rt

Development

  1. Assuming you have virtualenv installed, create a virtualenv to manage your python dependencies, and activate it. `virtualenv -v venv; source venv/bin/activate`

  2. Install [pypoetry](https://python-poetry.org/) to manage your dependencies. `pip install poetry`

  3. Install dependencies. `poetry install --no-root`

[tox](https://tox.readthedocs.io/en/latest/) runs all tests as its default target. Running tox by itself will run unit tests. Ensure you have a running redis, with the module loaded.

Contributing

Prior to submitting a pull request, please ensure you’ve built and installed poetry as above. Then:

  1. Run the linter. `tox -e linters.`

  2. Run the unit tests. This assumes you have a redis server running, with the [RedisAI module](https://redisai.io) already loaded. If you don’t, you may want to install a [docker build](https://hub.docker.com/r/redislabs/redisai/tags). `tox -e tests`

RedisAI example repo shows few examples made using redisai-py under python_client folder. Also, checkout ml2rt for convenient functions those might help in converting models (sparkml, sklearn, xgboost to ONNX), serializing models to disk, loading it back to redisai-py etc.

Metadata

Release files for redisai 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for redisai 1.3.0
File Size Uploaded Provenance Actions
redisai-1.3.0.tar.gz 16.0 kB Without provenance Details for redisai-1.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for redisai 1.3.0
File Interpreter ABI Platform Actions
redisai-1.3.0-py3-none-any.whl Python 3 none any Details for redisai-1.3.0-py3-none-any.whl

Total release size: 32.8 kB

Release files / redisai-1.3.0.tar.gz

Download URL redisai-1.3.0.tar.gz
Size 16.0 kB
Tags Source
SHA-256 checksum
How to use checksums
8d9efa3ead4d45ab480d70d98562658b458c6fa28c570e748035540ea2e392a0
BLAKE2b-256 checksum
How to use checksums
4001bed3f5f19a6b321c8a0e9096e978d9ea93f3bf2c99cbab3ac2d7d5bb2403
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.3.2 CPython/3.8.16 Linux/5.15.0-1031-azure

Release files / redisai-1.3.0-py3-none-any.whl

Download URL redisai-1.3.0-py3-none-any.whl
Size 16.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
22424cbe54353f8fb42ea09c93afd2158733e7224128b95cb19e7ae920048616
BLAKE2b-256 checksum
How to use checksums
e6a98953236caad42a712776bd05314e8a741233a4208f0fe8db4f45b39fad9c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.3.2 CPython/3.8.16 Linux/5.15.0-1031-azure

Security for redisai 1.3.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.

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page