TheR1sing3un opened a new pull request, #7736: URL: https://github.com/apache/paimon/pull/7736
## Purpose `dev/requirements.txt` currently pins `pyarrow>=16,<20; python_version >= "3.8"`. PyArrow 20 has been released, so the upper bound now blocks installation in any environment where a newer pyarrow is already resolved (e.g. via a downstream library, or via `pip install` on a fresh interpreter where 20+ is the latest wheel). There is no code reason for the cap: pypaimon already uses runtime version gates (`_pyarrow_lt_7`, `_pyarrow_gte_8`, etc.) inside `pyarrow_file_io.py` for the API differences it cares about. Removing the cap lets pip pick the latest compatible release without giving up any correctness guarantee that's actually enforced today. The 3.7-and-older line (`pyarrow>=6,<7; python_version < "3.8"`) is left untouched because pyarrow 6 is the last release with manylinux wheels for those interpreters. ## Linked issue N/A — surfaced when installing pypaimon into an environment that already had pyarrow 20. ## Tests * `pytest pypaimon/tests/file_io_test.py pypaimon/tests/rest/client_test.py` → green locally on pyarrow 16. * No code change; the existing CI matrix (3.6 / 3.10 / 3.11) will exercise pyarrow resolution end-to-end. ## API and format No public API change. No file format change. ## Documentation N/A. ## Generative AI disclosure Drafted with assistance from an AI coding tool; rationale verified against the runtime version gates already present in `pypaimon/filesystem/pyarrow_file_io.py`. -- 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]
