We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env_prefix
BaseSettings
Currently BaseSettings can take the following config values from its __init__ method:
__init__
pydantic-settings/pydantic_settings/main.py
Lines 47 to 54 in c05410f
Then these values are used if provided, else the ones from the SettingsConfigDict, e.g.:
SettingsConfigDict
Lines 109 to 114 in c05410f
Is there a reason why env_prefix isn't part of this scheme? If this is possible, I can make a PR implementing this.
The text was updated successfully, but these errors were encountered:
It's not only env_prefix. case_sensitive is not also included in __init__.
case_sensitive
I think we can include both of them. PR welcome.
Please remember to update the docs and add proper tests
Sorry, something went wrong.
Nice, will do
Successfully merging a pull request may close this issue.
Currently
BaseSettings
can take the following config values from its__init__
method:pydantic-settings/pydantic_settings/main.py
Lines 47 to 54 in c05410f
Then these values are used if provided, else the ones from the
SettingsConfigDict
, e.g.:pydantic-settings/pydantic_settings/main.py
Lines 109 to 114 in c05410f
Is there a reason why
env_prefix
isn't part of this scheme? If this is possible, I can make a PR implementing this.The text was updated successfully, but these errors were encountered: