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


   After seting 3.7 the default (#19317) the warning printed by
   Python during importing all providers (specifically apache beam)
   has slightly changed. Apparently collections.abc warning was
   a bit more "scary" - warning that it's 3.9 not 3.10 where the
   old collection imports will stop working (Note that actually
   this did not happen even in 3.10, apparently)
   
   This PR fixes the "known" warning message to match it but also
   a separate PR (https://github.com/apache/beam/pull/15850) was
   opened to Beam to get rid of the warnings altogether.
   
   Also seems 'dns` stopped generating this warning so I removed it.
   
   <!--
   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