Environment manager: Create Python terminal uses deactivate by default

[fin-gal]

Assume I have a venv virtual environment in the "venv Environments" section of the "Environment managers" view of the VSCode Python Activity bar.
Next to that environment is a little button that is supposed to create a new terminal, hover message says "Create Python Terminal", I assume with that environment activated.
When I click it, it successfully creates a new terminal but it seems to run by default the "deactivate" command.
Since no environment is activated that obviously leads to an error.

Is this on purpose or a bug?
This might be a duplicate of another issue even though the other issues descriptions seemed a bit different.

[karthiknadig]

This looks like a bug. To fix this correctly, I need the state of the terminal, waiting on this API to become available from core to solve this generically for autoactivation: microsoft/vscode#227467