You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/05 17:39:41 UTC
[GitHub] [airflow] potiuk opened a new pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
potiuk opened a new pull request #12839:
URL: https://github.com/apache/airflow/pull/12839
Part of #12838
<!--
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:
users@infra.apache.org
[GitHub] [airflow] potiuk closed pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
Posted by GitBox <gi...@apache.org>.
potiuk closed pull request #12839:
URL: https://github.com/apache/airflow/pull/12839
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #12839:
URL: https://github.com/apache/airflow/pull/12839#issuecomment-739494585
Let's see how the story evolves. I am afraid, that when we start announcing 2.0 and 1.10.14, we will be flooded with "Airflow does not install" issues.
And the more we protect against it, the better. In several places (unless of course https://github.com/pypa/pip/issues/9231 or similar workaround gets implemented).
I also would like all of us, committers to be aware that we have those problems with PyPI, so I do not end up as a person handling all such PyPI -related issues like #12824. I got redirected to as 'local PIP expert there, but honestly, I do not feel like a person that all the "PIP installation of Airflow is broken" should be directed to (or to any of the committers with that respect).
IMHO, the more vocal we are about it and proactively we tell about the problem the more likely our users will notice and downgrade PIP without involving slack conversations or opening issues.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #12839:
URL: https://github.com/apache/airflow/pull/12839#issuecomment-739494585
Let's see how the story evolves. I am afraid, that when we start announcing 2.0 and 1.10.14, we will be flooded with "Airflow does not install" issues.
And the more we protect against it, the better. In several places (unless of course https://github.com/pypa/pip/issues/9231 or similar workaround gets implemented).
I also would like all of us, committers to be aware that we have those problems with PyPI, so I do not end up as a person handling all such PyPI -related issues like #12824. I got redirected to as 'local PIP expert there", but honestly, I do not feel like a person that all the "PIP 20.3installation of Airflow is broken" should be directed to (or to any of the committers with that respect).
IMHO, the more vocal we are about it and proactively we tell about the problem the more likely our users will notice and downgrade PIP without involving slack conversations or opening issues.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #12839:
URL: https://github.com/apache/airflow/pull/12839#issuecomment-739494585
Let's see how the story evolves. I am afraid, that when we start announcing 2.0 and 1.10.14, we will be flooded with "Airflow does not install" issues.
And the more we protect against it, the better. In several places (unless of course https://github.com/pypa/pip/issues/9231 or similar workaround gets implemented).
I also would like all of us, committers to be aware that we have those problems with PyPI, so I do not end up as a person handling all such PyPI -related issues like #12824. I got redirected to as 'local PIP expert there", but honestly, I do not feel like a person that all the "PIP 20.3 installation of Airflow is broken" should be directed to (or to any of the committers with that respect).
IMHO, the more vocal we are about it and proactively we tell about the problem the more likely our users will notice and downgrade PIP without involving slack conversations or opening issues.
I just do not want to say "we've done enough to warn our users" situation like PIP did. Surely, we can blame our users for not reading the docs, but this is the last thing I would do.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on pull request #12839: Adds warning about ongoing problems wit PIP 20.3 to bug template
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #12839:
URL: https://github.com/apache/airflow/pull/12839#issuecomment-739494585
Let's see how the story evolves. I am afraid, that when we start announcing 2.0 and 1.10.14, we will be flooded with "Airflow does not install" issues.
And the more we protect against it, the better. In several places (unless of course https://github.com/pypa/pip/issues/9231 or similar workaround gets implemented).
I also would like all of us, committers to be aware that we have those problems with PyPI, so I do not end up as a person handling all such PyPI -related issues like #12824. I got redirected to as 'local PIP expert there", but honestly, I do not feel like a person that all the "PIP 20.3 installation of Airflow is broken" should be directed to (or to any of the committers with that respect).
IMHO, the more vocal we are about it and proactively we tell about the problem the more likely our users will notice and downgrade PIP without involving slack conversations or opening issues.
----------------------------------------------------------------
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:
users@infra.apache.org