Commands get run before python environment is activated

[User087]

When the "python.terminal.activateEnvironment": true setting is present, the Python environment in use is supposed to be automatically activated in all new terminals that get created. I find that with Run in Terminal, when running assigned commands for the first time since opening the editor (such that a run-in-terminal isn't already open), the assigned commands get executed in the new terminal first and then the automatic command to activate the environment gets executed, so only subsequent runs of the Run in Terminal commands get executed within the environment, but the first run doesn't. Can this be fixed so that the first time the commands are run, they only get executed after the environment is activated?

[kortina]

hmm, this does seem like a problem. Does anyone have ideas how other extensions handle this / if there is a canonical way of achieving this?