Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.x
What happened and how to reproduce it?
At the time of writing, it appears that the httpx library might not be actively maintained. There are a number of bug-fixes for httpx which have not landed, but which are present in httpx2 (forked from httpx==0.28.1).
Additionally, the maintainer of starlette (one of the key sub-dependencies of FastAPI) has confirmed that starlette will migrate to httpx2. So it seems the migration from httpx in FastAPI is an eventuality.
What you think should happen instead?
Any direct usage of httpx within airflow-core / the task-sdk / airflow's providers should probably migrate to httpx2.
The scope of this change is obviously large; but the migration of direct code reliance on httpx is relatively straightforward.
I'd imagine it would be good to add individual, well-defined / scoped sub-issues for this.
Operating System
No response
Deployment
No response
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.x
What happened and how to reproduce it?
At the time of writing, it appears that the
httpxlibrary might not be actively maintained. There are a number of bug-fixes forhttpxwhich have not landed, but which are present inhttpx2(forked fromhttpx==0.28.1).Additionally, the maintainer of
starlette(one of the key sub-dependencies ofFastAPI) has confirmed that starlette will migrate tohttpx2. So it seems the migration fromhttpxinFastAPIis an eventuality.What you think should happen instead?
Any direct usage of
httpxwithin airflow-core / the task-sdk / airflow's providers should probably migrate to httpx2.The scope of this change is obviously large; but the migration of direct code reliance on
httpxis relatively straightforward.I'd imagine it would be good to add individual, well-defined / scoped sub-issues for this.
Operating System
No response
Deployment
No response
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct