weiqingy opened a new issue, #980: URL: https://github.com/apache/flink-agents/issues/980
### Search before asking - [X] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description The build scripts invoke `pip` as a bare command. `pip` is not guaranteed to be on PATH: a Python install commonly exposes only `pip3`, or exposes pip solely as a module, in which case the bare command is not found and the script stops. There are five such call sites: - `tools/build.sh:104` — `pip install uv==0.11.0` - `tools/lint.sh:77` — `pip install -e "python[lint]"` - `tools/lint.sh:80` — `pip install -r python/requirements/linter_requirements.txt` - `tools/ut.sh:275` — `pip install -e ".[test]"` - `tools/ut.sh:276` — `pip install apache-flink~=${version}.0` `tools/build.sh:104` is the one that bites hardest. Unlike the others it does not sit behind the `command -v uv` check that `tools/lint.sh:67` and `tools/ut.sh:222` use, so it runs unconditionally and the Python half of the build fails before it starts: ``` ./tools/build.sh: line 104: pip: command not found ``` The four calls in `tools/lint.sh` and `tools/ut.sh` are in the no-`uv` fallback path and fail the same way once that path is taken. CI does not catch this because the runners provide a bare `pip`. It only shows up locally, which is where it costs a contributor the most time, since the failure looks like a broken build rather than a missing shim. Suggested fix: invoke pip through the interpreter, `python3 -m pip install ...`. `tools/install.sh` already uses `python -m pip` (for example at `:1387`), so this makes the rest of the scripts consistent with an existing in-repo convention. There is no behavior change where a bare `pip` already resolved, since both forms run the same pip module. Found while working on #976, unrelated to that change. **A PR is already open for this: #979.** Filing the issue for tracking rather than to hand the work out. ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- 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]
