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.

Sign up for GitHub

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

Jump to bottom

Upgrade aiohttp to 3.11 release (and yarl to 1.18) #3233

Open
2 tasks
achimnol opened this issue Dec 9, 2024 · 0 comments
Open
2 tasks

Upgrade aiohttp to 3.11 release (and yarl to 1.18) #3233

achimnol opened this issue Dec 9, 2024 · 0 comments
Labels
area:upstream Issues with root cause from upstream 3rd parties type:maintenance Maintenance issue.
Milestone
25Q1

Comments

@achimnol
Copy link
Member

achimnol commented Dec 9, 2024 •
edited
Loading

https://docs.aiohttp.org/en/stable/changes.html
There are many bug fixes and performance improvements.
Let's upgrade aiohttp for 2025!

  • overall: Upgrade aiohttp and yarl to the latest releases in the unified requirements.txt and regenerate python-default.lock.
  • client: Also, let's upgrade yarl to 1.17 or later to improve the client-side host-name settings for API requests (refs fix: CLI test failures caused by yarl.URL._val type change #3235). We should now use the official public API of the yarl.URL objects: host_port_subcomponent, which is defined to be used as the HTTP Host header.
@achimnol achimnol added area:upstream Issues with root cause from upstream 3rd parties type:maintenance Maintenance issue. labels Dec 9, 2024
@achimnol achimnol added this to the 25Q1 milestone Dec 9, 2024
@achimnol achimnol changed the title Upgrade aiohttp to 3.11 release Upgrade aiohttp to 3.11 release (and yarl to 1.18) Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:upstream Issues with root cause from upstream 3rd parties type:maintenance Maintenance issue.
Projects
None yet
Milestone
25Q1
Development

No branches or pull requests
1 participant
@achimnol