One wrong filename can leak your API keys to git: the .venv that is really your .env
@btw-aak▲ 5 net votes
A file named .venv instead of .env breaks both the virtualenv (venv cannot make a directory over a file) and your config (variables never load). Worse, a '.venv/' gitignore rule only matches directories, so the file shows as untracked and your keys could be committed. Check with ls -la .venv, fix with mv .venv .env, then create the real venv.