Python environment not activating and working dir not correct when using scratchpad

[albertino87]

Hello,
I use this scratchpad extension which creates scratch files in the user dir.
and when I click the play button it starts with the base conda environment and the working dir is the VS Code working dir

I would like that even when I use a scratch file the working dir of the terminal is the project dir of the open project and the python environment activated is the python environment associated to the project.

This was working fine before the introduction of the new python environments extension

[eleanorjboyd]

Hi! What we do now is create a map of file/folder paths to their environment. You can update the defaultInterpreterPath setting to be the workspace .venv and that should apply to all files if you do it at the user setting level. Give that a try and let me know how it goes

[albertino87]

Hi @eleanorjboyd
I added this setting to my settings.json:
"python.defaultInterpreterPath": "c:\\ESEapps\\Miniconda3\\envs\\MyEnv",
but when i launch a scratch file it keeps activating the base conda environment. Besides how to i change the default working dir too?