HyukjinKwon opened a new pull request, #56643: URL: https://github.com/apache/spark/pull/56643
### What changes were proposed in this pull request? Pin `black` to `22.6.0` (from `26.3.1`) in the branch-3.5 Python linter dependency install step in `.github/workflows/build_and_test.yml`. ### Why are the changes needed? The scheduled "Build (branch-3.5, Scala 2.13, JDK 8)" job runs master's `build_and_test.yml` against branch-3.5 source. Its linter step installs dependencies with `python3.9`. `black==26.3.1` only ships wheels that require Python >= 3.10, so pip fails on Python 3.9: ``` ERROR: Could not find a version that satisfies the requirement black==26.3.1 ... ERROR: No matching distribution found for black==26.3.1 ``` This breaks the branch-3.5 daily build at the "Install Python linter dependencies for branch-3.5" step before any linting runs. `black==22.6.0` is the version branch-3.5 already standardizes on (matches its `dev/pyproject.toml` required version) and installs cleanly on Python 3.9. ### Does this PR introduce any user-facing change? No. Infra/CI only. ### How was this patch tested? CI. Note: the exact branch-3.5 linter line cannot be exercised on a fork push because the scheduled branch-3.5 build uses master's workflow file against branch-3.5 source (dual-source), and a master PR does not run the branch-3.5 linter job. The change is a one-line dependency pin and `black==22.6.0` installs on Python 3.9 by construction. The second commit is a clearly-marked `[DO NOT MERGE]` CI trigger edit used for fork validation and should be dropped before merge. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
