potiuk opened a new pull request, #37849:
URL: https://github.com/apache/airflow/pull/37849
When going through various stages of installation of Airlfow in CI and PROD
image, we check several times if the packaging tools of ours are installed and
if they are installed in the right version. This is in order to make sure that
none of the installation steps upgraded them accidentaly (might happen when
--eager upgrade of pip or --highest resolution of uv are used).
This PR improves the speed of that (rather than installing the packages
again, we just check which version is already installed).
Similarly when constraints are already downloaded, we do not re-download
them again.
Also this change makes a consisten rename of the installation scripts to
reflect we have not only pip but also uv as packaging tool and installs both
`uv` and `pip` regardless which packaging tool we are using - which gives
anyone an opportunity to use either of the two tools if they wish.
Diagnostics is a bit nicer - rather than complaining with error when uv is
missing, prints information that it's not installed. We only show traces of
installation command (pip and uv) with `set -x` commands for diagnostics - we
do not show details of other internal commands.
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
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 an 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/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
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]
