Hi, The document says we could use `-pyarch` to upload python venv, but I found this is often problematic because users may not have the python binaries that fits the flink runtime environment.
For example, a user may upload a venv for macOS within the project, but the Flink cluster is using Debian, causing pyflink to fail. Is there some good practice to avoid this? Also, I wonder if it’s possible for pyflink to optionally provide an automatically created venv for each pyflink job? Thanks! Best, Paul Lam
