Increment PyArrow Bounds

[jrmccluskey]

PyArrow bounds need to be updated to include a version compatible with Python 3.14. This also increments the lower bound to remove versions that do not support any of Beam's currently supported Python versions.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @jrmccluskey, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the PyArrow dependency range to ensure compatibility with Python 3.14 and to align with currently supported Python versions by removing older, incompatible PyArrow versions from the lower bound. The changes involve adjusting the core dependency declaration and updating the test suite to reflect these new version constraints, thereby maintaining a robust and up-to-date dependency landscape.

Highlights

• PyArrow Dependency Update: The pyarrow dependency in sdks/python/setup.py has been updated to pyarrow>=6.0.1,<24.0.0. This change raises the minimum required version from 3.0.0 to 6.0.1 and extends the upper bound from 19.0.0 to 24.0.0.
• Tox Test Environment Adjustment: The tox.ini configuration for PyArrow testing environments has been modified. Older PyArrow versions (3, 9-10, 11-14) are no longer included in the test matrix, and new versions (19-23) have been added to ensure compatibility with the updated dependency bounds.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• sdks/python/setup.py
  • Updated the pyarrow dependency specification from pyarrow>=3.0.0,<19.0.0 to pyarrow>=6.0.1,<24.0.0.
• sdks/python/tox.ini
  • Modified the testenv definition py{310,311}-pyarrow-{...} to remove older PyArrow versions (3, 9-14) and include newer ones (19-23) in the test matrix.
  • Removed specific pandas and numpy dependency lines that were tied to the removed older PyArrow version 3.
  • Added new pyarrow dependency lines for versions 19 through 23.

Activity

• The pull request is currently marked as Work In Progress (WIP).
• The author has provided a standard contribution checklist, indicating the PR is awaiting further development or review.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[jrmccluskey]

@gemini-code-assist review

[gemini-code-assist]

Code Review

This pull request updates the PyArrow dependency bounds, primarily to ensure compatibility with Python 3.14. The changes correctly modify setup.py to adjust the version constraints and update the tox.ini test matrix to cover the new range of PyArrow versions. A minor adjustment in a test file seems to be a necessary fix related to these dependency changes. I've identified one potential issue in the tox.ini configuration that could lead to test failures.

[jrmccluskey]

The PreCommit failure is apache_beam/utils/multi_process_shared_test.py::MultiProcessSharedSpawnProcessTest::test_unsafe_hard_delete_autoproxywrapper and is red on master

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[jrmccluskey]

assign set of reviewers

[github-actions]

Assigning reviewers:

R: @damccorm for label python.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

Thanks!