potiuk opened a new pull request #20910:
URL: https://github.com/apache/airflow/pull/20910


   The `connexion` library has been vendored in because of requests
   library that used to have non-optional chardet LGPL dependency,
   however requests library had since released a version (which we
   helped to provide and convince the requests maintainer to merge)
   where chardet is an optional dependency (with mandatory
   charset_normalizer). This means that we do not need to vendor-in
   connexion any more.
   
   Also connexion after being somewhat abandoned, has been
   "revived" and there are active community now that maintains it -
   they released several new versions since 2.7.0 we used (2.10.0 is
   now the latest version, so we can upgrade to that version instead)
   
   <!--
   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/main/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/main/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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to