No-config - Python Debugger not contributing to built-in Terminal's environment

[liyanage]

I'm unable to get the Python Debugger to contribute to the built-in Terminal's output. I learned about that feature in a screenshot here: https://github.com/microsoft/vscode-python-debugger/wiki/No%E2%80%90Config-Debugging.

My ultimate goal is to get that no-config workflow documented there to work, but I am completely unable to get the Python Debugger to show up in that status popover that appears on hover over the zsh icon in the terminal pane, and that seems to be a prerequisite.

I verified that I have the latest version of the Python Debugger extension enabled. I also found this existing post about the issue: https://stackoverflow.com/questions/79383900/vscode-python-not-contributing-to-terminal-environment. I tried the solution in there of force-enabling the pythonTerminalEnvVarActivation experiment, that didn't enable it either.

Confusingly, the instructions for no-config on the wiki page noted above also specifically say to force that same experiment off because it's not compatible, so that contradiction is extra confusing.

Even ignoring that using no-config debugging is my ultimate goal, has anybody else hit this issue of Python Debugger not showing up in the popover and contributing to the environment, and how did you fix it?

[karthiknadig]

@liyanage Do you have terminal.integrated.shellIntegration.enabled ticked?

[liyanage]

@liyanage Do you have terminal.integrated.shellIntegration.enabled ticked?

@karthiknadig yes I have that enabled. I also temporarily tried without my .zshrc in case anything in there makes it not work.

[karthiknadig]

@anthonykim1 do you know what we can check to make sure this is working for zsh?

[karthiknadig]

@liyanage Can you confirm the version of the debugger extension you have? Do you see the same issue with the latest pre-release version ( 2025.1.2025022401 ).

Can you share a screenshot of the terminal? just want to make sure that shell integration is working on that machine.

[anthonykim1]

Applying environment variable at shell integration time defaults to false, so checking if shell integration is active or inactive at this point might not get us far. (If we later go add&pass in mutator option, then yes checking if shell integration is active or inactive will be useful)

Reference:

	/**
	 * Options applied to the mutator.
	 */
	export interface EnvironmentVariableMutatorOptions {
		/**
		 * Apply to the environment just before the process is created. Defaults to false.
		 */
		applyAtProcessCreation?: boolean;

		/**
		 * Apply to the environment in the shell integration script. Note that this _will not_ apply
		 * the mutator if shell integration is disabled or not working for some reason. Defaults to
		 * false.
		 */
		applyAtShellIntegration?: boolean;
	}

We could start using explicit EnvironmentVariableMutatorOption and applyAtShellIntegration if we detect shell integration is active more explained: #631

Since applyAtShellIntegration comes after applyAtProcessCreation, it would be more "safer" route to set environment variables.

[liyanage]

The Python Debugger extension version is 2025.0.1.

I'm seeing the same result with the pre-release version 2025.1.2025022401.

Here is a screenshot of the Terminal pane. How can you tell if the shell integration is working?

[anthonykim1]

I don't think whether shell integration is working or not is decisive of this issue atm.

I'm wondering if the environment variables that are needed for this "no-config" debugging feature are even set for you in the first place.

Can you set your log level to trace and look for env, specifically environmentVariableCollections?
It will look something like:

Also the part where it says applyAtProcessCreation and applyAtShellIntegration would be useful too:
So something like:

"environmentVariableCollections":[["vscode.git",[["GIT_ASKPASS",{"variable":"GIT_ASKPASS","value":"/home/developer/.vscode-server-insiders/cli/servers/Insiders-ac0e8f0f32e3de145dc3aa11d8182f208a05397f/server/extensions/git/dist/askpass.sh","type":1,
"options":

{"applyAtProcessCreation":true,"applyAtShellIntegration":false}}],

[liyanage]

Thanks for continuing the investigation!

I had to reinstall macOS for an unrelated reason, and now it just works. I have no idea why or what was broken, but unfortunately I can't provide any more debugging data now.

I'm happy to close this if there's nothing actionable...

[karthiknadig]

Thank @liyanage for the update. We can close this. Do keep us posted if you run into any other issues.