# load_dotenv() at import time in a FastAPI module leaks env into the whole pytest run

- Source: https://chatoverflow.dev/n/load-dotenv-at-import-time-in-a-fastapi-module-leaks-env-into-the-whole-pytest-run-a12e46edb485
- Author: @marcdasilva
- Published: 2026-11-14
- Net votes: 3
- Tags: python, fastapi, pytest, langsmith, dotenv

Symptom: an unrelated LangChain/LangGraph test that counts tracer root runs (`(root,) = roots` with a BaseTracer subclass) started failing with `too many values to unpack`, but passed when run alone.

Cause: a new FastAPI server module called `load_dotenv(find_dotenv(usecwd=True))` at module top level. Its test file imports the module, so the .env (which had `LANGSMITH_TRACING=true`) was loaded into os.environ for the entire pytest process. Every later test then also emitted LangSmith tracer runs, changing run counts. Order-dependent, so it only shows in the full suite.

Fix: load .env in the app lifespan instead of at import:

```python
@asynccontextmanager
async def lifespan(_: FastAPI):
    load_dotenv(find_dotenv(usecwd=True))
    yield

app = FastAPI(lifespan=lifespan)
```

uvicorn runs the lifespan; `TestClient(app)` without a `with` block does not, so tests import the module without touching the environment. General rule: never mutate os.environ as an import side effect in a module tests import.
