Issue with VS Code custom sequences 'OSC 633 ; ... ST' in Python shell for Ubuntu in WSL 2

[vladjohnson]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: Version: 1.91.0 (system setup)
• OS Version: Windows_NT x64 10.0.19045

Hi there, I am having issues with VS Code custom sequences making their way into the Python shell. For instance: ]633;E;quit()]633;D;0]633;A>>> ]633;B]633;C. I've tried disabling the shell integration, but it does not work. Please help!

Steps to Reproduce:

1. Open a .py file and run python file using the "Run Python File" button on the right upper corner.
2. In the opened terminal, type python or python3.

[VSCodeTriageBot]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[vladjohnson]

Problem still exists. Thank you!

[Tyriar]

@anthonykim1 is this stuff not behind an opt-in setting atm?

[vladjohnson]

@anthonykim1 @Tyriar thank you so much for helping out!

[anthonykim1]

Thanks for filing the issue @vladjohnson

@Tyriar Yeap, this is not behind a setting atm.

I'm bit surprised about this because we don't enable this for windows folks at all.
We use

if sys.platform != "win32":
    sys.ps1 = PS1()

to filter out windows folks and only attach such sequence for non-windows users who use Terminal Python REPL.

Now I am wondering if "win32" is not sufficient.

Can you please

import sys

and print

sys.platform

and let me know of the value?

I'm guessing we may have to handle it better for WSL.

[vladjohnson]

@anthonykim1 sure thing! The platform value is 'linux'. I am running Ubuntu 20.04 LTS in WSL 2. Thanks!

[anthonykim1]

@vladjohnson Thanks for this!

So I basically need to be more through than
sys.platform != "window32"
and sort out that user can be in 'linux' environment via Windows.

I'll mark this as bug, and let you know once I have the fix. Thank you

[vladjohnson]

Thank you! Appreciate it, @anthonykim1