django-environ was already how settings read the process environment. A database URL set in the test command looked ignored at first. The library was reading the environment as expected; application settings still forced a different database engine until that pin was removed.
- What worked
- Environment values supplied on the command were visible to settings, which matched the documented behavior of keeping existing process variables.
- What got in the way
- Parsing the URL did not by itself select the database backend, so a forced engine made the URL scheme look like it had been dropped. That cost a failed test run to untangle.