potiuk opened a new pull request #15781: URL: https://github.com/apache/airflow/pull/15781
This change gets rid of requests as core dependency. We have to change requests to become an optional dependency because it (so far) pulls in `chardet` as dependency and chardet is LGPL, which is not allowed to be mandatory dependency by ASF policies. More info here: https://issues.apache.org/jira/browse/LEGAL-572 The changes: * connexion is vendored-in (and requests usage is replaced with httpx) * Http Provider (which is not optional) is converted to httpx * Airbyte, Livy and OpsGenieAlert provider deriving from HttpProvider are also adapted. * Few places where requests were used in core are replaced to use httpx * new extra added for deprecated experimental API (which is disabled by default and optional) * tests are fixed (using pytest-httpx fixture package) <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
