DanielLeens commented on issue #12461: URL: https://github.com/apache/seatunnel/issues/12461#issuecomment-5814908853
Classification: E / CLI source-install isolation.\n\nThanks for the precise proposal. Current dev confirms that seatunnel-cli/setup.sh directly runs python3 -m pip install -e ".[dev]", so the system-interpreter pollution and old editable-build failure are both real. I found the focused implementation at #12464; it is the single path for this issue.\n\nThe PR scope is appropriate: project-local .venv creation/reuse, fallback after cleanup, in-environment build-tool upgrade, documentation, and isolated script tests, while distribution launchers and manual pip installs remain unchanged. Please keep the Python 3.10+ check, ensure no system pip is invoked after virtual-environment creation is attempted, and retain the failure path that names the missing venv support rather than silently changing the caller environment.\n\nThe Build check is currently queued and the PR is BLOCKED, so this remains in progress rather than complete. Please keep discussion and any follow-up on #12464; no is sue metadata change is 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]
