pythonredis/redis-py #3630Not a task: already works

Dependency on old pyjwt

envgap__redis__redis-py-3630

Original GitHub issue ↗Dated source checkout ↗Opened 2025-05-02

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: a1f3cabf3e4e009c810d15e3972119287d8ad96f
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

redis/redis-py #3630 · read the original issue

With `5.3` an explicit dependency on PyJWT 2.9 got introduced via https://github.com/redis/redis-py/pull/3462

Is there a specific reason for this, or could this be `"PyJWT>=2.9.0"`?

I noticed this, as updating `redis` would downgrade `pyjwt` for me.

```
$ uv lock --upgrade-package redis==5.3.0
Resolved 329 packages in 470ms
Updated pyjwt v2.10.1 -> v2.9.0
Updated redis v5.2.1 -> v5.3.0
```

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]