[SPARK-54465][INFRA] Remove build_python_connect35.yml GitHub Action job
#53178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to remove a broken and misleading
build_python_connect35.ymlGitHub Action job.Note that this doesn't mean that they are incompatible. This is literally the GitHub Action infra issue.
Why are the changes needed?
build_python_connect35has been broken over 4 months since 2025-07-23.The root cause is PySpark 4.1 and PySpark 3.5 requirements are different. Especially,
pyarrow,grpcio, andgoogleapis-common-protos.spark/python/docs/source/getting_started/install.rst
Lines 155 to 165 in ed00d04
spark/python/docs/source/getting_started/install.rst
Lines 225 to 235 in c125aea
Since there is no way to install both dependencies in a single Python, we had better remove this for now. We need an alternative way.
Does this PR introduce any user-facing change?
No behavior change because this is a removal of already broken CI. This CI is only invokable in
apache/sparkrepository.spark/.github/workflows/build_python_connect35.yml
Line 33 in 7f5478c
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.