Olawoyin007 opened a new pull request, #888: URL: https://github.com/apache/flink-agents/pull/888
Linked issue: #863 ### Purpose of change `install.sh` did not offer the 0.3.0 release (shipped June 19th), and it rejected Python 3.12 even though 0.3.0 supports it. - Add `0.3.0` to `FLINK_AGENTS_SUPPORTED_VERSIONS` and make it the recommended default, matching https://flink.apache.org/downloads/#apache-flink-agents (0.3.0 ships JARs for Flink 1.20 / 2.0 / 2.1 / 2.2, same matrix as 0.2.x). - Make the Python upper bound follow the selected release instead of a hardcoded `<3.12`: 0.1.x/0.2.x keep `>=3.10,<3.12`, while 0.3.0+ accepts Python 3.12 (its wheels publish `requires-python >=3.10,<3.13`). The version-mismatch messages now print the bound that actually applies. The version choice happens in stage 1 (`plan_flink_agents`) before Python resolution in stage 2 (`plan_pyflink`), so `FLINK_AGENTS_VERSION` is always settled when `validate_python_bin` runs. One known edge left as-is: on Python 3.12 with Flink 1.20/2.0, `apache-flink` has no cp312 wheel on PyPI, so pip falls back to the sdist. That combination fails at pip time with a clear resolver message rather than being pre-blocked by the installer. ### Tests - Reworked the 3.12/3.13 cases in `tools/test/unit/validate_python_bin.bats` to cover both bounds (3.12 rejected for 0.2.x, accepted for 0.3.0+, 3.13 still rejected) and updated the default-version assertion in `dry_run_extra.bats`. - `bash tools/test/run.sh`: all 149 tests pass. - Manually verified on Linux with Python 3.12.3: accepted with the 0.3.0 default, correctly rejected with `--flink-agents-version 0.2.1`. ### API No public API changes; installer script only. ### Documentation - [ ] `doc-needed` - [x] `doc-not-needed` (quickstart docs already state "Python 3.10, 3.11 or 3.12") - [ ] `doc-included` -- 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]
