Python and/or Anaconda version: 3.8.3 Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda Jupyter server running: Local Expected behaviour Should work fine with the conda environment Actual behaviour VSCode is not recognising the environment Not running the cells....
I think the first issue, about VSCode not recognizing the right Python version in the env, may have been due to some misshap happened when uninstalling anaconda and installing miniforge. Manually adding the interpreter works fine, even though it's strange it's not detected automatically. The se...
I guess what I'm trying to say is, I've narrowed the issue down to VSC not recognizing my commands, ignoring them (somehow), or something is entirely f***d. I have tried googling for solutions for over 2 MONTHS now, and still have been unable to find a solution. Needless to say,...
After you get this stable update I would kindly ask all of you to remove the extensions.verifySignature: false from your settings, because we want signature verification to not be disabled and to hear if there are any other issues that we might have not fixed. Thank you very much! 👍 2...
@Esger<https://github.com/Esger>, sorry for not getting back to you on this until now. Can you please confirm that you are unable to initialise a repository using the following steps: - Create a new folder foo - In terminal navigate inside the foo folder and type code-insiders . - ...
The issue must be with the debugging engine not recognizing whatever output it's expecting from GDB/MI. Perhaps the debugging engine should consider other criteria besides this before prematurely terminating the debugging session? I'd suggest re-opening this issue, or I can create a new one if...
"python.pythonPath": "C:\\Users\\pconwell\\.virtualenvs\\ridgeplots-0xoO3BBx\\Scripts\\python.exe" } Which will not work at all. VS Code is (presumably) recognizing the virtual environment correctly as the code will run manually from terminal AND the correct virtual environment is showing...