If the vscode python interpreter is set to pipenv environment and you open a terminal in vscode, source $ VENV_LOCATION / bin / activate will be executed without permission and you will enter the pipenv environment.
In that case, the environment variables in the pipenv environment set in .env are not reflected, which is a problem.
Even if the pipenv environment is selected in the python interpreter setting of vscode, the pipenv environment will not be activated automatically on the terminal. (I want to hit pipenv run or pipenv shell later)
Open the vscode setting screen and open
Search for python.terminal.activateEnvironment and uncheck enable.
It was just this, but in Japanese it did not hit with my search ability, so I will write it for the time being.
Recommended Posts