algolia / algolia/algoliasearch-client-python
[bug]: Using algoliasearch v3 and need to use `async-timeout>=4.0.3` but only `async-timeout@^3` is supported
- Dominant language
- Python
- Stars
- 207
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
### Description
We kindly request a maintenance release of algoliasearch v3 (e.g., v3.0.1) that supports `async-timeout>=4.0.3` while maintaining all other functionality. This is critical because our project needs to integrate `redis-py` which requires the newer `async-timeout` version, but we cannot migrate to `algoliasearch` v4 yet due to its incomplete migration guide, lack of comprehensive documentation, and inferior developer experience compared to v3. This dependency conflict is currently blocking our ability to implement Redis functionality, which is essential for our infrastructure. A small maintenance update would benefit many users who are still using v3 in production systems while planning controlled migrations to v4 on their own timelines.
I would really appreciate your support on this 🙏
### Client
All
### Version
3
### Relevant log output
```shell
```
Contributor guide
Research direction
Start by inspecting the Python v3 package's dependency metadata for the async-timeout constraint and review the existing test setup. Confirm that the updated constraint remains compatible with the client and redis-py, then run the relevant test suite and verify that the package can be released without changing other functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, redis
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100