potiuk opened a new pull request, #48210: URL: https://github.com/apache/airflow/pull/48210
The setuptools 78.0.1 started to fail old packages that had dash metadata keys and had only .sdist installation. This caused failures of three of our dependencies: * json-merge-patch * pykylin * pyspark The `josn-merge-patch` is a library released in 2017 (v 0.2) that implements the [RFC7386](https://datatracker.ietf.org/doc/html/rfc7386) standard of patching json. It has been used in only one place in our repo in google provider, in order to merge json patches (well - obvious :). Seems like the best approach is to vendor-in the code (70 lines or so) rather than rely on 2017-released package The `pykylin` and `pyspark` are more problematic because we should not vendor those in (of course) - instead we upper-bind setuptools and add the packages to the list of packages that are build by uv with no build isolation The original issue with setuptools 78.0.1 is tracked in the https://github.com/pypa/setuptools/issues/4910 <!-- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
