New Terminal output adding spaces and % resulting in cut off when activating Python environments (venv)

[slimsnerdy]

Does this issue occur when all extensions are disabled?: Yes/No
Yes (only Python/Pylance installed since needed)

• VS Code Version: 1.81.1
• OS Version: macOS Ventura 13.5.1

Steps to Reproduce:

1. Open Command Palette --> Python: Create Environment --> Venv --> Python (I chose Python 3.10.12 64-bit) --> requirements.txt (leave unchecked) click OK

2. Now create a new terminal; this is the strange part.. Sometimes it will add a % and a whole bunch of spaces when "activating" the environment.. look at the line with source.. the_slim_fatty_p% rod/.venv/bin/activate
   That is actually a bunch of spaces. Right click the Terminal window and "Toggle Size to Content Width" to see.

Sometimes creating a new terminal does not do this behavior and no spaces are added and that weird %.
This happens on new machines too. New projects from scratch. Python and macOS only tested.
Very random behavior; quickest way to test is click the plus icon on the bottom right to open new terminals so it activates in rapid succession and most of the time it actually does not add the spaces to the output. But every 4 or 5 clicks it does.. I have no idea.

CORRECT BEHAVIOR:

INCORRECT BEHAVIOR:

Tasks

Preview Give feedback

No tasks being tracked yet.

[karrtikr]

@meganrogge We simply send the command source <activate> to VS Code, how it appears in terminal is not something we have control over.

[karrtikr]

• @slimsnerdy Can you provide the Python logs?

  Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

  XXX
  

[slimsnerdy]

nevermind I had to select "Python" from the dropdown

[karrtikr]

Regarding the main issue in hand, it can be confirmed from the logs indicate that Python sent the right command in terminal, so transferring this issue to VS Code as indicated here: #192018 (comment).

[slimsnerdy]

warning] Microvenv failed as it is using proposed API which is constantly changing [TypeError: this.context.getEnvironmentVariableCollection is not a function

That issue should go away once you update your pre-release version of the extension., it's duplicate of microsoft/vscode-python#21831.

thank you; I will check

[Tyriar]

This is happening because you're using sendText before the shell is initialized. The only way to fix this is via a timeout (which is unreliable) or via a yet to come executeCommand API. The % stuff is just that messing up zsh's standup startup

[karrtikr]

FWIW we do wait on terminal to open:

Regardless, this issue should not be happening with microsoft/vscode-python#11039, closing this.