Detect the default Python version in CLI, not in dstack-server

[jvstme]

Problem

If the user omits the python property in the run configuration, dstack is supposed to use the Python version installed in the user's environment. This allows dstack environments to be more similar to users' local environments.

However, dstack currently detects the Python version in dstack-server. While this works for the simplest setups, in many setups dstack-server runs separately from users' environments, so users actually get the Python version from the dstack-server environment, not their local environment.

Solution

Detect the default Python version in dstack CLI, not in dstack-server.

[easedeath]

Hi can i work on this issue?

[peterschmidt85]

Hi can i work on this issue?

@easedeath You don't need to ask. If you know how to fix this, just send a PR! Thank you

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.