kevinveenbirkenbachandClaude Opus 5 e4c188f3fc refactor(env): let setdefault own the env override ...

EnvBuilder.setdefault already reads os.environ.get(key).strip() and prefers it over the computed value. Three handlers repeated that check in front of eb.set: four dead lines each plus an import, restating a contract that lives one module over. If setdefault ever changes, the three copies do not follow.

Behaviour is identical and was measured on both paths: each handler yields the same derived value as before, and with os.environ[KEY] set the override still wins. The only change in flow is that an overridden value is now computed and discarded, costing one df or /proc read per make dotenv.

The host-path guard in registry_cache_max_size stays: it prevents a df on an empty path, which is a different concern from the override.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-07 17:05:50 +02:00

..

__init__.py

refactor(structure): move prefix-grouped files into named subfolders

2026-07-14 20:00:03 +02:00

admin_password.py

refactor(structure): move prefix-grouped files into named subfolders

2026-07-14 20:00:03 +02:00

blobstore_max.py

refactor(env): let setdefault own the env override

2026-08-07 17:05:50 +02:00

direct_mem.py

refactor(structure): move prefix-grouped files into named subfolders

2026-07-14 20:00:03 +02:00

heap.py

refactor(env): let setdefault own the env override

2026-08-07 17:05:50 +02:00