tuhaihe commented on PR #1434: URL: https://github.com/apache/cloudberry/pull/1434#issuecomment-3857821233
Thanks for the review and feedback! I agree that installing Python dependencies implicitly in the build system is not ideal in the long term, especially with PEP 668 and distro packaging policies. For this PR, I’d like to keep the current behavior for compatibility reasons (it is consistent with the existing build logic and avoids breaking current users and CI environments). This change mainly addresses the Ubuntu 24.04 build failure while preserving backward compatibility. As a follow-up, I plan to propose a cleaner approach: - Remove implicit pip installation from the build process. - Recommend users to install Python dependencies explicitly via `pip3 install -r python-dependencies.txt` (or via venv / distro packages). - Update the build documentation accordingly and make the build fail fast if required Python modules are missing. This would align better with reproducible builds and packaging best practices, but it should be done in a phased manner to avoid disrupting existing workflows. How about this? @leborchuk @gfphoenix78 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
