Describe the issue
When setting up environment with vscode extension but also in databricks cli itself there is no option to choose what python version to use. For example I want to use 3.12.10 but the cli automatically chooses 3.12.14(due to uv python install 3.12).
It would be good to use python version that we choose instead of automatically chosen. It can be because some organizations do not want to add patch version automatically or the new version might be behind firewall.
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
- Run
databricks environments setup-local --profile xxx --cluster-id xxx --debug
- See error
Expected Behavior
There should be an option or environment variable to choose python version
Actual Behavior
It uses 3.12 and propagates it to uv which tries to install the newest one.
OS and CLI version
windows and cli 1.14.0
Is this a regression?
Not sure which version before but it just used virtual environment created by me.
It might also be related to databricks runtime 18 LTS. Previously I was working with 16.4
Describe the issue
When setting up environment with vscode extension but also in databricks cli itself there is no option to choose what python version to use. For example I want to use 3.12.10 but the cli automatically chooses 3.12.14(due to uv python install 3.12).
It would be good to use python version that we choose instead of automatically chosen. It can be because some organizations do not want to add patch version automatically or the new version might be behind firewall.
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
databricks environments setup-local --profile xxx --cluster-id xxx --debugExpected Behavior
There should be an option or environment variable to choose python version
Actual Behavior
It uses 3.12 and propagates it to uv which tries to install the newest one.
OS and CLI version
windows and cli 1.14.0
Is this a regression?
Not sure which version before but it just used virtual environment created by me.
It might also be related to databricks runtime 18 LTS. Previously I was working with 16.4