[Python] Why does python main.py fail with MinIO initialization error while running in VSCode...

I'm encountering a strange issue where my Python application runs successfully in VSCode but fails when executed directly via the terminal using the command:

python main.py


The error seems to be related to the MinIO client initialization, which is initialized at the top of the file like this:

minio_client = connect_minio.MinioClient()


However, no exception is thrown in VSCode, and everything works as expected.

Here are some key points about my setup and observations:

• I'm using .env files to load environment variables via python-dotenv.
• The path to .env is resolved dynamically based on the script location:
  from logisticsVerification import start
  env_path = Path(__file__).resolve().parent / ".env"
  load_dotenv(dotenv_path=env_path)

the start.py

minioclient = MinioClient(bucket_name=bucket_name)

• 
  When running from the terminal, it appears that the .env file is not loaded correctly, leading to missing environment variables needed by [MinioClient].
  
  
• 
  In contrast, VSCode debugging mode runs without any issues, suggesting that there might be differences in:
  
  • Working directory
  • Python interpreter used
  • Environment variable loading behavior

I have already checked:

• The output of os.getcwd() and sys.path inside both environments.
• That the .env file exists and contains all required keys.
• That the same Python interpreter is used (via which python).

Yet I’m still unable to pinpoint why the module initialization behaves differently.

Code Snippet:


from imageProcess import connect_minio
env_path = Path(__file__).resolve().parent / ".env"
load_dotenv(dotenv_path=env_path)

minio_client = connect_minio.MinioClient() # Fails here when run from terminal

What I Want to Know:


Why would the same script behave differently when run in VSCode vs terminal? What are the common reasons behind such discrepancies (e.g., working directory, environment variables, sys.path, or PYTHONPATH) — and how can I make the terminal execution consistent with VSCode’s behavior?

Any help or suggestions for further debugging would be greatly appreciated.

I change my

from logisticsVerification import start


below the

load_dotenv(dotenv_path=env_path)


everything will be ok. but I don't know why vscode can run before.

Continue reading...