I have the same issue when my .env is placed in the root of the VScode workspace. It affected me when using it in jupyter notebook. My current workaround is to use _ = load_dotenv(override=True) when loading environment variables from the file.

It seems that vscode automatically source the .env file to create the environment variables when the file is placed at the root. I didn't know that before.