Had an issue start with VSCode the last week or so, and not sure if there's just something wrong with my system, my vscode config, or if there's just a vscode bug.
To start, I'm running on OSx Sequoia 15.3.1. I also have Pyenv installed to help manage all the disparate python versions I'm using across my various venvs.
If I have a single folder open in my workspace, and I go to open a Terminal, the venv will activate correctly and I can proceed as normal.
However, if I have multiple folders open in the workspace, each with their own interpreter specified, When I open a terminal for one of the folders VSCode will say that the venv has been activated, but in actuality it will have failed. It will display the venv name at the start of the command prompt as if it has been activated, but running which python will return the path of the default system interpreter. The venv has to be manually activated for things to be able to run properly.
If anyone has any ideas or thoughts as to where I can start looking, that would be a godsend.
