Environment gets activated after debugger starts (hence debugging with conda envs fail)

[crackcomm]

Environment data

• VS Code version: Just updated
• Extension version (available under the Extensions sidebar): Just updated
• OS and version: Windows 10
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7, Conda3
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Issue

Use Debug Python: Current File...

> cd ...
[...]
    from matplotlib import afm, cbook, ft2font, rcParams, get_cachedir
ImportError: DLL load failed: The specified module could not be found.

>D:/Anaconda3/Scripts/activate
>conda activate base

Terminal stays open so I can click again the play icon and it works because conda activate base activated Python environment just AFTER the debugger FAILED to start.

Thank you.

[karrtikr]

Can you please be more clear here. I am not sure I understand the issue here.

Terminal stays open so I can click again the play icon and it works

• ... what works?
• Please provide file content, complete exact terminal display (for eg. what does [...] represent in cd ...) and clarify the steps to reproduce.

[crackcomm]

• ... debugger?
• Use Debug Python: Current File...

[karrtikr]

Please fill the issue template and provide the requested information. The issue is not clear.

[crackcomm]

No, thanks.

[karrtikr]

Closing this as sufficient clarification info was not provided.

[karrtikr]

I understand the issue, however i need more info to reproduce this, as I have asked for before.

• Relevant file content, complete terminal display (for eg. what does [...] represent in cd ...)

[crackcomm]

[...] represents code that was removed.

[karrtikr]

I understand that. What I am asking is what is the code that was removed? (Leave out personal credentials if you have to)

[crackcomm]

This code was removed because there is no issue with the code.

The issue is

>D:/Anaconda3/Scripts/activate
>conda activate base

Is executed AFTER execution of the code.

[karrtikr]

The reason I was asking this is because AFAICS there are cases where it should not matter if it's activated after or not. For eg. this was terminal in my case,
cd [...] && cmd /C "set "PYTHONIOENCODING=UTF-8" && set "PYTHONUNBUFFERED=1" && C:\ProgramData\Anaconda3\python.exe [...]\ptvsd_launcher.py --default --client --host localhost --port [...]"

Notice this,
C:\ProgramData\Anaconda3\python.exe
The python executable is directly being used here, so it does not matter if environment is activated before or not.

What i wanted to understand was the reason that it mattered in your case (so I can reproduce & confirm it). Regardless, I understand the core issue here.

[crackcomm]

To replicate use any library that loads DLL for example graphviz, pytorch, tensorflow.

[crackcomm]

In my example it was matplotlib.

[DonJayamanne]

@crackcomm
Apologies for the confusion, I understand the issue.
Basically the environment is getting activated after the debugger has started.
We'll be tracking this here #4568

[DonJayamanne]

Solution identified in microsoft/vscode#67692 could fix this.

Updated Solution - Use conda run.

[bryceschober]

@DonJayamanne Can you clarify your proposed solution of conda run? Are you proposing a modified launch configuration? Could you provide an example?

[DonJayamanne]

@bryceschober this isn't a change to the launch configuration. Instead of running user code using <python executable> <user code> we'll be using conda run <env name> python <user code>.

[AlexH415]

I seem to have this problem too. I don't understand what is meant by "Instead of running user code using we'll be using conda run python .". Is this a fix I can apply myself now? If so, how do I do it please?

[damdaepark]

@DonJayamanne You mean this conda run solution will be updated soon?

[DonJayamanne]

That is the plan.

[kimadeline]

Closing in favour of #10626