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


   We have recently seen a number of issues created by users who
   tried to install airflow with poetry or pip-tools or who had
   successes with using the latest pip 20.3.3. This change aims
   to update the 'note' content and make sure installation
   instructions are consistent everywhere, so that new users
   are warned against using anything else than PIP and that they
   are aware about potential problems with 'pip 20.3' and ways
   to mitigate the problems.
   
   This responds to the needs of confused users such as
   one in https://github.com/apache/airflow/issues/13711#issuecomment-761694781
   
   <!--
   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]


Reply via email to