Activate the CONDA env in the VS Code workspace

[gwd666]

Whenever starting a REPL for which the selected Python interpreter would be one in a CONDA environment created (
via conda create --prefix ... ) as subfolder right there in the VS Code workspace the VS Code python extension is not capable of activating therefore "using" that respective environment, with Start REPL?
I tried everything from .vscode/settings.json to .vscode/.launch.json
It will always end up with starting a new Terminal REPL even in case I already activated the CONDA env in the Terminal followed by

Warning:
This Python interpreter is in a conda environment, but the environment has not been activated. 

So it does notice that this is a CONDA env (of the python interpreter I want to use here) but there is no (at least I have not discovered it) way to convince the VS Code Python extension to activate that selected one!
Because since it is a --prefix environment and not one that would be discoverable by a 'plain vanilla' conda activate environment_name BUT only from within the ${worspace_root} via
conda activate .\myCondaEnv the Python extension startup attempt always fails with environment NOT found and the "hint" to look at the available envs via conda env list
PLEASE come up with or in case I just have not discovered the correct method to apply here then PLEASE document properly how to achieve THIS!? Feel free to point me to the correct method ...
Thanks ...

[brettcannon]

Did you specify a Python version so that a Python interpreter was installed into your conda environment (as documented in the environments)?

If you launch VS Code from your terminal with your conda environment activated then we will use it directly. You can also try opting into our environment discovery experiment to see if that helps as we have been reworking our environment discovery code (we are hoping to open that code up to all users in the next month or so).

Also note that the warning you got is not from us; that's most likely coming from conda itself.

[gwd666]

Hi @brettcannon - thanks for the swift reply and your tips.
As mentioned I am writing exactly for the reason that this env was created with conda create --prefix path\to\workspace, so without --name (as in the documentation you provided a link to), which seems to make it "undiscoverable" somehow, but since I like to keep my conda envs and my projects and workspaces "close" that is quite a common use case imo.
I am sorry to have to say that even starting VSC with code . from within the activated conda env from a Miniconda CMD (NOT Anaconda as mentioned in the docu, in case that makes a diff) prompt, does not improve the functionality, still same issues. I would not mind if VSC could handle this type of activation from the prompt tbh for now.
But it seems that one [I] can expect some changes within a month or so. The env discovery experiment would be a certain branch, or so?
Still thumbs up -> and thanks for that otherwise great extension!

[brettcannon]

If you turn on our insiders channel you will get a more up-to-date version of the extension which includes the new discovery code. If that doesn't work then this is a bug that we should fix.