Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): Lock aioredis to <2 #98

Closed
wants to merge 1 commit into from
Closed

chore(deps): Lock aioredis to <2 #98

wants to merge 1 commit into from

Conversation

bravier
Copy link
Contributor

@bravier bravier commented Jul 30, 2021

aioredis v2.0.0 has just been released:
https://pypi.org/project/aioredis/2.0.0/

It breaks aioredlock with the following errors:

AttributeError: module 'aioredis' has no attribute 'create_redis_pool'
AttributeError: module 'aioredis' has no attribute 'errors'

I propose to lock the aioredis version aioredlock requires to
<2 (latest before v2.0.0 is v1.3.1).

`aioredis` v2.0.0 has just been released:
https://pypi.org/project/aioredis/2.0.0/

It breaks `aioredlock` with the following errors:
```
AttributeError: module 'aioredis' has no attribute 'create_redis_pool'
AttributeError: module 'aioredis' has no attribute 'errors'
```

I propose to lock the `aioredis` version `aioredlock` requires to
<2 (latest before v2.0.0 is v1.3.1).
@bravier bravier changed the title chore(deps): Lock aioredis to 1.3.1 chore(deps): Lock aioredis to <2 Jul 30, 2021
@gtmanfred
Copy link
Collaborator

I don't really want to pin this. I would prefer to fix the usage and switch to using from_url if it is available.

@bravier
Copy link
Contributor Author

bravier commented Aug 5, 2021

Okay I understand. I proposed to pin aioredis as a quick fix while waiting for a full support of v2.0.0.
I'll close this PR then.

@bravier bravier closed this Aug 5, 2021
@bravier bravier deleted the chore/lock-aioredis-version branch August 5, 2021 13:21
@gtmanfred
Copy link
Collaborator

Thanks, we don't pin the version, so applications that are using it should be able to pin it, and not be overwritten. I am going to make sure to pin <3 when i finish fixing for support for 2.0.0 which hopefully i will be able to tomorrow.

see #99

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants