Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Beam's Python SDK harness boot entrypoint may fail when python is not accessible, but python3 is. #26958

Closed
1 of 15 tasks
tvalentyn opened this issue May 31, 2023 · 0 comments · Fixed by #28046
Closed
1 of 15 tasks
Assignees
Labels
bug done & done Issue has been reviewed after it was closed for verification, followups, etc. good first issue P3 python

Comments

@tvalentyn
Copy link
Contributor

tvalentyn commented May 31, 2023

What happened?

The code in

if err := execx.Execute("python", args...); err != nil {

assumes the Python executable is always python, which seems to not work on Ubuntu system. We should be able to detect that and handle this case gracefully.

There were also asks in the past to consider making Python path configurable . We could introduce an environment variable that controls the path to interpreter, defer to it if specified, if not - try python, if that fails, try python3.

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug done & done Issue has been reviewed after it was closed for verification, followups, etc. good first issue P3 python
Projects
None yet
3 participants