Configure which Python interpreter assest bundels uses

[JCZuurmond]

Describe the issue

Asset bundles uses the default Python interpreter on Windows; I want to choose which python interpreter it uses.

Motivation

To chose which Python version it is using and to not globally install additional dependencies, like bdist_wheel and setuptools-scm.

Configuration

Windows laptop

Steps to reproduce the behavior

Please list the steps required to reproduce the issue, for example:

1. Run databricks bundle deploy ... -> uses default windows Python interpreter

Expected Behavior

I expect to configure which interpreter asset bundles uses.

Actual Behavior

It selects the default python interpreter

OS and CLI version

Databricks CLI v0.210.1
Windows 10 Pro

Debug Logs

Relevant log line

time=2023-12-08T14:49:52.474+01:00 level=DEBUG source="background.go 31}" msg="running: C:\\Users\\<USER NAME>\\AppData\\Local\\Microsoft\\WindowsApps\\python3.exe setup.py bdist_wheel" pid=11680 mutator=seq mutator=build mutator=seq mutator=artifacts.BuildAll mutator=seq mutator=artifacts.Build(default) mutator=artifacts.whl.Build(default)

[JCZuurmond]

I was able turn circumvent this issue:

It looks like #805 gives preferences to python3 over python. On my Windows machine python3 points to the pre-installed python on Windows, where python points to the Python version I installed (also python 3). I rerouted the python3 command to the python command that I prefer.

[andrewnester]

You could also define a custom artifact section in your bundle configuration to point to different Python location or even different way of building package by customising build option.

artifacts:
  default:
    type: whl
    build: /path/to/your/python -m build
    path: /path/to/your/package

[nfx]

@JCZuurmond is it always the case on windows, btw?

[JCZuurmond]

TBH I do not know. I usually work on Linux based machines.

When I use a Windows machine, I always install Python myself instead of using the one that is distributed with Windows because that usually causes problems. I expect that I could have installed Python as a python3 executable as well, with preference over the pre-installed one in the PATH. In that case, I would not have ran into this problem