potiuk commented on issue #31823: URL: https://github.com/apache/airflow/issues/31823#issuecomment-1588086695
Ok. Few more questions then (I want to see how we can update the description so that you can get it right. > To have repeatable installation, however, we keep a set of "known-to-be-working" constraint files in the orphan constraints-main and constraints-2-0 branches. We keep those "known-to-be-working" constraints files separately per major/minor Python version. You can use them as constraint files when installing Airflow from PyPI. Note that you have to specify correct Airflow tag/version/branch and Python versions in the URL. Could you please explain what "repeatable installation" means for you? In other words when you are upgrading a provider on top of airflow, do you have expectations to have the same (i.e. repeatable) installation of airflow as with the original provider? Or do you want to have different, (non repeatble) installation with new provider? > Also... the presence of the providers themselves in the pip-constraints file leads in that direction too. We have been doing all our provider upgrades by just updating the pip-constraints... So you already know that provider is in the constraints. And yet you are suprised that that when you are trying to install different version, than the one that you have in constraints. Is this what you are trying to tell? In other words you expect this `pip install apache-airflow-providers-google=10.0.1 --constraints = <file>` where the file contains ` apache-airflow-providers-google=10.0.0` to work ? What is your expectation to happen? -- 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]
