-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Pin down multidict #6550
Pin down multidict #6550
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I like the idea.
@Dreamsorcerer this probably needs a change note, though. |
Looks like it is already affecting some others. Maybe make a new 3.8 release tomorrow to minimise the impact? |
multidict 6.0.2 should fix problems. |
aiohttp 3.8.2 was just released and it restricts the multidict dependency to >=4.5,<6.0. Is this still intended? |
@jakob-keller Please see PR #6950 to re-bump it. |
The `multidict` dependency used to be `multidict >=4.5, < 7.0` in `aiohttp` v3.8.1, but was pinned down to `multidict >=4.5, < 6.0` in `aiohttp` v3.8.2 (#6550) in an attempt to help avoid new errors. However, https://github.com/python/bedevere/ uses `multidict==6.0.2` so the requirements resolution fails with `aiohttp==3.8.2`: ```console ERROR: Cannot install -r requirements.txt (line 1) and multidict==6.0.2 because these package versions have conflicting dependencies. The conflict is caused by: The user requested multidict==6.0.2 aiohttp 3.8.2 depends on multidict<6.0 and >=4.5 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ``` https://github.com/hugovk/bedevere/actions/runs/3095794573/jobs/5010600772 This patch makes it possible to have `multidict` v6 installed in the same env as `aiohttp` v3.8.3, as with `aiohttp` v3.8.1. Partially related to closed #6600 and merged #6550. PR #6950 Co-Authored-By: Sviatoslav Sydorenko <webknjaz@redhat.com>
With the new errors coming in, it might be a good idea to pin this down in the 3.8 release.