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


   Recent 3.6 image had a problem with building documentation with
   eager upgrade and updating to the latest python images.
   TypeError("unsupported operand type(s) for +: 'SSL_VERIFY_PEER' and
   'SSL_VERIFY_FAIL_IF_NO_PEER_CERT'")
   
   We are trying to diagnose and solve the problem properly but this
   PR attempts to check if the problem is solved (seems so) if we
   use Python 3.7 to build documentation (this requires changing the
   default version used on CI to be Python 3.7 for all CI tests,
   because in most cases we are building only one image for PR
   and run all tests and docs building using the same image.
   
   <!--
   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