You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you happen to call config.load() twice, the latter fails to read from default_files. This leads to difficult to troubleshoot issues like:
pydantic_core._pydantic_core.ValidationError: 1 validation error for AppConfig
SECRET_KEY
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.8/v/missing
This probably is avoidable by very reasonably saying that we shouldn't be calling config.load() twice. However the docs suggest using config.django_manage() which itself calls config.load(), so in that case at least it is unavoidable.
It looks like the method to check for files loaded data in version 5.0 should be updated.
The text was updated successfully, but these errors were encountered:
ruamel.yaml is only loaded if a yaml file has been specified as the config file. It is optional in the sense that, if you don't want to load yaml files, you don't need it.
roharvey
changed the title
repeating config.load() fails to read default_files, ruamel.yaml not really optional
repeating config.load() fails to read default_files
Aug 22, 2024
If you happen to call
config.load()
twice, the latter fails to read from default_files. This leads to difficult to troubleshoot issues like:This probably is avoidable by very reasonably saying that we shouldn't be calling
config.load()
twice. However the docs suggest usingconfig.django_manage()
which itself callsconfig.load()
, so in that case at least it is unavoidable.It looks like the method to check for files loaded data in version 5.0 should be updated.
The text was updated successfully, but these errors were encountered: