Python-dotenv bug - Githubissues

Mykola-CI / slipknot-fan-hub

Join the legion of Slipknot loving Maggots! This community-driven site is a gathering place for Slipknot fans. All built on a reliable tech stack including Django and a relational database

1 stars 0 forks source link

Python-dotenv bug #11

Open Mykola-CI opened 4 months ago

Mykola-CI commented 4 months ago

Date of discover: 20th April 2023

Context: manage.py runserver expected to serve local.py settings at DEBUG=True and serve production.py settings at DEBUG=False. DEBUG is assigned in .env file and retrieved by .load_dotenv() function and get by os.getenv() method.
Problem description: When DEBUG is reset to False, manage.py keeps serving local.py

Mykola-CI commented 4 months ago

Test Findings:

print statements under load_dotenv() show that .env file is not correctly loaded. Whatever DEBUG value the load_dotenv() function loads True until VS Code is restarted. After restart it picks up pre-set False. However, when again changed to True load_dotenv() keeps loading False.
Running CLI commands from outside VS Code integrated terminal. Tested different scenarios: everything works fine and changing True to False and vice versa triggers between local.py and production.py as set in manage.py

Conclusion:

The problem is related to the operational bug of VS Code integrated Terminal. Most likely it is a bug connected with caching environment variables by the development environment in my VS Code.

Decision

The issue to be moved to Done with reservation column of the Progress Board BUT not Closed until the project submission.