---
title: "valkey · PyPI"
description: "!https://pypi.org/project/valkey/"
date: 2025-02-17
published: true
tags:
  - python
  - thought
template: link
---


<div class="embed-card embed-card-external">
  <a href="https://pypi.org/project/valkey/" class="embed-card-link" target="_blank" rel="noopener noreferrer">
    <div class="embed-card-image">
      <img src="https://pypi.org/static/images/twitter.abaf4b19.webp" alt="valkey — Python client for Valkey forked from redis-py" loading="lazy">
    </div>
    <div class="embed-card-content">
      <div class="embed-card-title">valkey</div>
      <div class="embed-card-description">Python client for Valkey forked from redis-py</div>
      <div class="embed-card-meta">PyPI &middot; pypi.org</div>
    </div>
  </a>
</div>


python bindings for valkey, forked from redis.

one notable difference I see from redis is that you can install with libvalkey to autmatically get faster parsing support.

> For faster performance, install valkey with libvalkey support, this provides a compiled response parser, and for most cases requires zero code changes. By default, if libvalkey >= 2.3.2 is available, valkey-py will attempt to use it for response parsing.

``` bash
pip install "valkey[libvalkey]"
```