Unable to install DW - tries to unnecessarily install Python and Jupyter

[Josverl]

Environment data

• VS Code version: Version: 1.92.2 (user setup)
• Data Wrangler Extension version: XXX
• Jupyter Extension version (available under the Extensions sidebar): v1.6.0
• Python Extension version (available under the Extensions sidebar): v2024.7.0
• OS (Windows | Mac | Linux distro) and version: Windows_NT x64 10.0.22631
• Pandas version: 2.2.2
• Python and/or Anaconda version: Python 3.11.9
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Kernel - Local python Environment (

Expected behaviour

To work

Actual behaviour

• Fails to work - instead tries to install the Python and VSCode extensions that are already installed

• View Jupyter Variable : Fails

• View df from notebook : option not shown

Steps to reproduce:

• install
• follow the walkthrough ( and pull a .csv out of thin air on step 2 ) I have tried and given up several times, even on a brand new machine it again fails to install and work properly Switching back and forth to preview versions , does not help either.

One thing to note is that I make use of multiple different vscode profiles. The Python Extension is not installed in all of them ( as that is kind of the goal of different profiles)

When in a notebook with a pandas df, there is no Option to launch DW

Logs

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

``` Visual Studio Code (1.92.2, undefined, desktop) Jupyter Extension Version: 2024.7.0. Python Extension Version: 2024.12.3. Pylance Extension Version: 2024.8.2. Platform: win32 (x64). Workspace folder d:\mypython\micropython-stubber, Home = c:\Users\josverl ```

[pwang347]

Hi @Josverl, thank you for opening this issue! Could you please check if this discussion applies to you? https://github.com/microsoft/vscode-data-wrangler/issues/129#issuecomment-1922177014

What you're seeing generally indicates that Data Wrangler might not be running on the same process as your Python/Jupyter VS Code extensions. From what I have seen, it's usually been because of the setting above - let me know if it resolves it for you. Thanks!