Lowercases SCREAMING_SNAKE_CASE names and keeps the underscores: SESSION_COOKIE_AGE → session_cookie_age. Same words, same separators, only the case changes.
This direction comes up when constants or environment variables have to become ordinary variables, dictionary keys, database columns or YAML/TOML settings, for example moving Django-style settings into a pydantic model or turning a list of env vars into config file keys.
String.Result.SESSION_COOKIE_AGE = 1209600
EMAIL_HOST_USER = "noreply@example.com"
_INTERNAL_TOKEN_TTL = 60session_cookie_age = 1209600
email_host_user = "noreply@example.com"
_internal_token_ttl = 60The three setting names are lowercased; the e-mail value and the numbers are unchanged, and _INTERNAL_TOKEN_TTL keeps its leading underscore as _internal_token_ttl.
HTTP_2_ENABLED → http_2_enabled.DEBUG, True) are not matched.Settings like EMAIL_HOST_USER become fields named email_host_user on a BaseSettings class, and pydantic still reads the upper-case environment variable because matching is case-insensitive by default.
When a service moves from many environment variables to one config.yaml, the lowercased names are the usual keys in that file.
CURRENT_TIMESTAMP if they appear in the text.That lowercases everything, including values, string contents and keywords like True. This page changes only the SCREAMING_SNAKE_CASE identifiers.
DEBUG converted?No, a name needs at least one underscore to be matched. Lowercase it yourself.