Close the gap between actual client behavior and the project's compatibility claims.
Scope:
- Audit auth, DB selection, close/reset behavior, decode settings, and error types against redis-py expectations.
- Document which paths are truly redis-py compatible, which are raw-command fallback, and which remain unsupported.
- Update README/benchmark copy to avoid claiming 1:1 parity before the compatibility harness proves it.
- Add a feature-parity tracker that references concrete tested behavior.
Why:
The project should not claim redis-py compatibility beyond what is test-backed.
Close the gap between actual client behavior and the project's compatibility claims.
Scope:
Why:
The project should not claim redis-py compatibility beyond what is test-backed.