You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conda run -n <env name> python --version will run the python interpreter in the <env name> directory.
Actual behaviour
I'm on version 1.41 and it's already using "conda run", which doesn't work on my system. As you can see in the picture, the python version should be 3.8.0, but "conda run" only invokes the base environment python of version 3.7.5.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
XXX
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
XXX
The text was updated successfully, but these errors were encountered:
Originally reported by @mind6
https://github.com/microsoft/vscode-python/issues/8827#issuecomment-571840198
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): N/AExpected behaviour
conda run -n <env name> python --version
will run the python interpreter in the<env name>
directory.Actual behaviour
I'm on version 1.41 and it's already using "conda run", which doesn't work on my system. As you can see in the picture, the python version should be 3.8.0, but "conda run" only invokes the base environment python of version 3.7.5.

Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: