Adam Yoblick

Hi all, this is a Visual Studio fix, not a PTVS one. Their team had some urgent fixes they had to make that had higher priority than this one. They...

I'm not sure, let me dig into the exact command VS is running and I'll report back.

Looks like the Python Tools extension invokes it, and indeed with `--diff`. https://github.com/microsoft/PTVS/blob/main/Python/Product/PythonTools/PythonTools/Editor/Formatting/PythonFormatterBlack.cs#L30

I spoke with Pavel about this and it seems this is working locally but doesn't work when installing through VS setup. We need to investigate further. See the following: -...

Ok I did some investigation and here's what I found: - In the latest VS public preview (Version 17.6.0 Preview 1.0), the Python/Native Debugging option is missing. - I checked...

This has been fixed but I'm not able to verify the fix locally until I get a VS installer from the PR into VS. That will probably happen tomorrow.

I tested this with the installer provided by the Visual Studio insertion PR, and the UI issue is indeed fixed in the installer:  So now I'm moving on to...

And the missing files are in the correct place after installing: 

@StellaHuang95 can you try to repro this whenever you have some time? I just want to make sure this isn't an urgent blocker now. Thanks :)

Does the environment still get created? Unknown event received seems like a pylance issue, we probably need to present this to the team then.