Why Is There A Conda Glitch Specific To VSCode Terminal, But Not Normal Terminal?
Solution 1:
I have experienced the same in the Windows operating system, and I figured out why that happens in windows, and I think it's the same reason in Mac also;
the problem is when you close the vscode with the opened terminal when you restart the terminal opens automatically, but at there whatever environment you have configured into that directory by using .vscode does not execute.
you can see that, because there is just the terminal without activation any env.
but if there is no terminal opened at the start, when you open the terminal it executes the environment activation command [most of the time].
NOTE:
the best way to solve this, whether or not the terminal has opened is;\
Click the little + icon I have circled by blue,
then then it created a new terminal, the definitely your environment activates on time. Also, you can close the first terminal by selecting it in dropdown and click bin icon
this same problem appears even in the python virtual environment and pip environments. \
check that out this trick in Mac, because I'm not really sure.
Solution 2:
In VS Code, the internal terminal it uses is integrated from the system's own terminal. Therefore, if the system terminal can be used, the internal terminal of VS Code can also be used.
Usually, when VS Code uses the python environment, the modules are stored in "lib\site-packages" of the corresponding python environment.
You could use the command "pip show pandas" in the VS Code terminal to check the installation location of the module "pandas":
In addition, it is recommended that you find the installation package of the module "pandas" in this environment, and then try to delete it and reinstall it to avoid problems due to damaged or incompatible files inside the module:
If it still doesn't work, please try to restart VS Code to let it reload the terminal.
Post a Comment for "Why Is There A Conda Glitch Specific To VSCode Terminal, But Not Normal Terminal?"