MonkeyCanCode opened a new pull request, #3510: URL: https://github.com/apache/polaris/pull/3510
<!-- ๐ Describe what changes you're proposing, especially breaking or user-facing changes. ๐ See https://github.com/apache/polaris/blob/main/CONTRIBUTING.md for more. --> Currently the Makefile is default to `python3` (which can be any python3 version users may had set on their setup), to allow user to use a specific version of Python for building as well testing, we should consider make python version configurable without modifying symbolic link for python3 or modify Makefile. Here is a sample use-case I tried earlier to validate if we can actually use python3.14 for polaris: ``` โ polaris git:(makefile_custom_python) โ PYTHON=python3.14 make client-regenerate Setting up Python virtual environment at .venv... Virtual environment created. Installing UV and project dependencies into .venv... Requirement already satisfied: pip in ./.venv/lib/python3.14/site-packages (25.3) Collecting uv>=0.9.0 Using cached uv-0.9.26-py3-none-macosx_11_0_arm64.whl.metadata (11 kB) Using cached uv-0.9.26-py3-none-macosx_11_0_arm64.whl (20.2 MB) Installing collected packages: uv Successfully installed uv-0.9.26 Resolved 63 packages in 8ms Resolved 63 packages in 4ms ร Failed to build `pyroaring==1.0.3` ... help: `pyroaring` (v1.0.3) was included because `apache-polaris:dev` (v1.4.0) depends on `pyiceberg` (v0.10.0) which depends on `pyroaring` ``` ## Checklist - [x] ๐ก๏ธ Don't disclose security issues! (contact [email protected]) - [x] ๐ Clearly explained why the changes are needed, or linked related issues: Fixes # - [x] ๐งช Added/updated tests with good coverage, or manually tested (and explained how) - [x] ๐ก Added comments for complex logic - [x] ๐งพ Updated `CHANGELOG.md` (if needed) - [x] ๐ Updated documentation in `site/content/in-dev/unreleased` (if needed) -- 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]
