[codespaces] Python virtual environment setup

[danieljurek]

When launching Python codespaces alerts come up before build... What's the earliest time we could/should run the vscode azd restore command? Python projects should also communicate with the Python extension, if possible, and indicate the appropriate interpreter (this could get interesting with multiple python projects)

Example error message in first run:

Example error message in first debugging run:

To fix:

1. Run the "Restore API" task to get a python virtual environment on the instance
2. Ctrl+Shift+P > Python: Select Interpreter ... select the one created in the restore step

[rajeshkamal5050]

@philliphoff do we see this extension issue on VSCode?

[weikanglim]

This reproduces on devcontainer and Codespaces.

The root cause seems to be that VSCode server is creating a settings.json in /home/vscode/.vscode-server/data/Machine/settings.json containing the following settings:

{
	"python.defaultInterpreterPath": "/usr/local/bin/python",
	"python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
	"python.formatting.blackPath": "/usr/local/py-utils/bin/black",
	"python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
	"python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
	"python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
	"python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
	"python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
	"python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
	"python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
}

which /usr/local/bin/python doesn't exist. Commenting out this file fixes the issue. Still investigating further...

[rajeshkamal5050]

@weikanglim @danieljurek any updates on the investigation? Is this a blocker for Codespaces release in Jan?

[vhvb1989]

This reproduces on devcontainer and Codespaces.

The root cause seems to be that VSCode server is creating a settings.json in /home/vscode/.vscode-server/data/Machine/settings.json containing the following settings:

{
	"python.defaultInterpreterPath": "/usr/local/bin/python",
	"python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
	"python.formatting.blackPath": "/usr/local/py-utils/bin/black",
	"python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
	"python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
	"python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
	"python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
	"python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
	"python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
	"python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
}

which /usr/local/bin/python doesn't exist. Commenting out this file fixes the issue. Still investigating further...

@weikanglim , have you tried overriding the python.defaultInterpreterPath setting within the template folder settings?
Maybe if you set it to python3 instead of python ?

[weikanglim]

@rajeshkamal5050 This was fixed in devcontainers/features#258. Verifying before closing out.

[weikanglim]

Verified working as expected. Closing.