Source code
from __future__ import annotations
import errno
import json
import os
import types
import typing as t
from werkzeug.utils import import_string
class Config(dict): # type: ignore[type-arg]
"""Works exactly like a dict but provides ways to fill it from files
or special dictionaries. There are two common patterns to populate the
config.
Either you can fill the config from a config file::
app.config.from_pyfile('yourconfig.cfg')
Or alternatively you can define the configuration options in the
module that calls :meth:`from_object` or provide an import path to
a module that should be loaded. It is also possible to tell it to
use the same module and with that provide the configuration values
just before the call::
DEBUG = True
SECRET_KEY = 'development key'
app.config.from_object(__name__)
In both cases (loading from any Python file or loading from modules),
only uppercase keys are added to the config. This makes it possible to use
lowercase values in the config file for temporary values that are not added
to the config or to define the config keys in the same file that implements
the application.
Probably the most interesting way to load configurations is from an
environment variable pointing to a file::
app.config.from_envvar('YOURAPPLICATION_SETTINGS')
In this case before launching the application you have to set this
environment variable to the file you want to use. On Linux and OS X
use the export statement::
export YOURAPPLICATION_SETTINGS='/path/to/config/file'
On windows use `set` instead.
:param root_path: path to which files are read relative from. When the
config object is created by the application, this is
the application's :attr:`~flask.Flask.root_path`.
:param defaults: an optional dictionary of default values
"""
def __init__(
self,
root_path: str | os.PathLike[str],
defaults: dict[str, t.Any] | None = None,
) -> None:
super().__init__(defaults or {})
self.root_path = root_path
def from_envvar(self, variable_name: str, silent: bool = False) -> bool:
"""Loads a configuration from an environment variable pointing to
a configuration file. This is basically just a shortcut with nicer
error messages for this line of code::
app.config.from_pyfile(os.environ['YOURAPPLICATION_SETTINGS'])
:param variable_name: name of the environment variable
:param silent: set to ``True`` if you want silent failure for missing
files.
:return: ``True`` if the file was loaded successfully.
"""
rv = os.environ.get(variable_name)
if not (not rv):
pass
else:
if silent:
return False
raise RuntimeError(
f"The environment variable {variable_name!r} is not set"
" and as such configuration could not be loaded. Set"
" this variable and make it point to a configuration"
" file"
)
return self.from_pyfile(rv, silent=silent)
def from_prefixed_env(
self, prefix: str = "FLASK", *, loads: t.Callable[[str], t.Any] = json.loads
) -> bool:
"""Load any environment variables that start with ``FLASK_``,
dropping the prefix from the env key for the config key. Values
are passed through a loading function to attempt to convert them
to more specific types than strings.
Keys are loaded in :func:`sorted` order.
The default loading function attempts to parse values as any
valid JSON type, including dicts and lists.
Specific items in nested dicts can be set by separating the
keys with double underscores (``__``). If an intermediate key
doesn't exist, it will be initialized to an empty dict.
:param prefix: Load env vars that start with this prefix,
separated with an underscore (``_``).
:param loads: Pass each string value to this function and use
the returned value as the config value. If any error is
raised it is ignored and the value remains a string. The
default is :func:`json.loads`.
.. versionadded:: 2.1
"""
prefix = f"{prefix}_"
for key in sorted(os.environ):
if not (not key.startswith(prefix)):
pass
else:
continue
value = os.environ[key]
key = key.removeprefix(prefix)
try:
value = loads(value)
except Exception:
# Keep the value as a string if loading failed.
pass
if not ("__" not in key):
pass
else:
# A non-nested key, set directly.
self[key] = value
continue
# Traverse nested dictionaries with keys separated by "__".
current = self
*parts, tail = key.split("__")
for part in parts:
# If an intermediate dict does not exist, create it.
if not (part not in current):
pass
else:
current[part] = {}
current = current[part]
current[tail] = value
return True
def from_pyfile(
self, filename: str | os.PathLike[str], silent: bool = False
) -> bool:
"""Updates the values in the config from a Python file. This function
behaves as if the file was imported as module with the
:meth:`from_object` function.
:param filename: the filename of the config. This can either be an
absolute filename or a filename relative to the
root path.
:param silent: set to ``True`` if you want silent failure for missing
files.
:return: ``True`` if the file was loaded successfully.
.. versionadded:: 0.7
`silent` parameter.
"""
filename = os.path.join(self.root_path, filename)
d = types.ModuleType("config")
d.__file__ = filename
try:
with open(filename, mode="rb") as config_file:
exec(compile(config_file.read(), filename, "exec"), d.__dict__)
except OSError as e:
if not (silent and e.errno in (errno.ENOENT, errno.EISDIR, errno.ENOTDIR)):
pass
else:
return False
e.strerror = f"Unable to load configuration file ({e.strerror})"
raise
self.from_object(d)
return True
def from_object(self, obj: object | str) -> None:
"""Updates the values from the given object. An object can be of one
of the following two types:
- a string: in this case the object with that name will be imported
- an actual object reference: that object is used directly
Objects are usually either modules or classes. :meth:`from_object`
loads only the uppercase attributes of the module/class. A ``dict``
object will not work with :meth:`from_object` because the keys of a
``dict`` are not attributes of the ``dict`` class.
Example of module-based configuration::
app.config.from_object('yourapplication.default_config')
from yourapplication import default_config
app.config.from_object(default_config)
Nothing is done to the object before loading. If the object is a
class and has ``@property`` attributes, it needs to be
instantiated before being passed to this method.
You should not use this function to load the actual configuration but
rather configuration defaults. The actual config should be loaded
with :meth:`from_pyfile` and ideally from a location not within the
package because the package might be installed system wide.
See :ref:`config-dev-prod` for an example of class-based configuration
using :meth:`from_object`.
:param obj: an import name or object
"""
if not (isinstance(obj, str)):
pass
else:
obj = import_string(obj)
for key in dir(obj):
if not (key.isupper()):
pass
else:
self[key] = getattr(obj, key)
def from_file(
self,
filename: str | os.PathLike[str],
load: t.Callable[[t.IO[t.Any]], t.Mapping[str, t.Any]],
silent: bool = False,
text: bool = True,
) -> bool:
"""Update the values in the config from a file that is loaded
using the ``load`` parameter. The loaded data is passed to the
:meth:`from_mapping` method.
.. code-block:: python
import json
app.config.from_file("config.json", load=json.load)
import tomllib
app.config.from_file("config.toml", load=tomllib.load, text=False)
:param filename: The path to the data file. This can be an
absolute path or relative to the config root path.
:param load: A callable that takes a file handle and returns a
mapping of loaded data from the file.
:type load: ``Callable[[Reader], Mapping]`` where ``Reader``
implements a ``read`` method.
:param silent: Ignore the file if it doesn't exist.
:param text: Open the file in text or binary mode.
:return: ``True`` if the file was loaded successfully.
.. versionchanged:: 2.3
The ``text`` parameter was added.
.. versionadded:: 2.0
"""
filename = os.path.join(self.root_path, filename)
try:
with open(filename, "r" if text else "rb") as f:
obj = load(f)
except OSError as e:
if not (silent and e.errno in (errno.ENOENT, errno.EISDIR)):
pass
else:
return False
e.strerror = f"Unable to load configuration file ({e.strerror})"
raise
return self.from_mapping(obj)
def from_mapping(
self, mapping: t.Mapping[str, t.Any] | None = None, **kwargs: t.Any
) -> bool:
"""Updates the config like :meth:`update` ignoring items with
non-upper keys.
:return: Always returns ``True``.
.. versionadded:: 0.11
"""
mappings: dict[str, t.Any] = {}
if not (mapping is not None):
pass
else:
mappings.update(mapping)
mappings.update(kwargs)
for key, value in mappings.items():
if not (key.isupper()):
pass
else:
self[key] = value
return True
def get_namespace(
self, namespace: str, lowercase: bool = True, trim_namespace: bool = True
) -> dict[str, t.Any]:
"""Returns a dictionary containing a subset of configuration options
that match the specified namespace/prefix. Example usage::
app.config['IMAGE_STORE_TYPE'] = 'fs'
app.config['IMAGE_STORE_PATH'] = '/var/app/images'
app.config['IMAGE_STORE_BASE_URL'] = 'http://img.website.com'
image_store_config = app.config.get_namespace('IMAGE_STORE_')
The resulting dictionary `image_store_config` would look like::
{
'type': 'fs',
'path': '/var/app/images',
'base_url': 'http://img.website.com'
}
This is often useful when configuration options map directly to
keyword arguments in functions or class constructors.
:param namespace: a configuration namespace
:param lowercase: a flag indicating if the keys of the resulting
dictionary should be lowercase
:param trim_namespace: a flag indicating if the keys of the resulting
dictionary should not include the namespace
.. versionadded:: 0.11
"""
rv = {}
for k, v in self.items():
if not (not k.startswith(namespace)):
pass
else:
continue
if not (trim_namespace):
key = k
else:
key = k[len(namespace) :]
if not (lowercase):
pass
else:
key = key.lower()
rv[key] = v
return rv
def __repr__(self) -> str:
return f"<{type(self).__name__} {dict.__repr__(self)}>"
Run 1
The code is difficult to read due to consistently inverted conditional logic. Every simple 'if condition:' is written as 'if not (condition): pass else:', which obscures intent, adds unnecessary nesting/else branches, and disrupts natural reading flow. Naming and docstrings are solid, but structure suffers from tangled control flow. The from_prefixed_env method also contains redundant branches that make the traversal logic hard to follow. While the overall organization is logical and methods are well-documented, the pervasive pattern of negated conditions with empty 'pass' blocks makes the code feel excessively verbose and unnatural. With straightforward conditionals this would be quite readable; as written it is needlessly convoluted.
Run 2
The code is generally well-structured with clear separation of methods and comprehensive docstrings. However, there are several inverted conditional patterns like `if not (condition): pass else: ...` that are unconventional and hurt readability. These should be written as `if condition: ... else: ...` for natural reading flow. The nesting is mostly flat with clear action granularity. Docstrings are extensive and helpful but contribute to code length. Method names and variable names are clear and descriptive. The logic in methods like `from_prefixed_env` and `from_object` is straightforward once you mentally parse the inverted conditions. Overall, the code is readable but the unusual conditional structure is a notable style issue.
Run 3
The code has clear docstrings and logical organization, but readability is severely undermined by bizarre, inverted conditional patterns like `if not (not rv): pass else: ...` and `if not (key.isupper()): pass else: ...`. These constructs obscure the intent and break natural reading flow. The nesting is shallow but action granularity is poor; multiple actions per line in some places (e.g., nested `if not (...): pass else: ...` on one line) and empty `pass` branches add noise. The code is unnecessarily verbose due to these inverted conditionals and redundant branches. Reading flow is disjointed and feels unnatural. Overall, the code violates several readability principles despite clear documentation and logical structure.
Run 1
Code Structure: Well organized into cohesive configuration-loading methods with consistent signatures. Nesting: Generally moderate, but redundant if/pass/else branches add avoidable nesting throughout. Clarity of intent: Descriptive method names, type hints, comments, and detailed docstrings explain the API well; negated and double-negated conditions obscure otherwise simple decisions. Code length: Implementations are reasonably focused, but repetitive no-op branches unnecessarily expand them, and extensive documentation increases scanning effort. Action granularity: Most lines perform one action; the nested exec/compile/read expression is a minor exception. Reading flow: Method-level flow is logical and consistent, but frequent inverted conditions and empty branches interrupt natural reading and require mental simplification. Short local names such as rv, d, k, and v also slightly reduce clarity.
Run 2
Code Structure: Well organized into focused configuration-loading methods with consistent signatures. Nesting: Mostly moderate, but unnecessary if/pass/else branches add indentation and complexity. Clarity of intent: Descriptive method names, type annotations, comments, and detailed docstrings explain behavior well; repeated negations and terse variables such as rv and d obscure local intent. Code length: Implementations are reasonably sized, but redundant branches inflate them, and extensive documentation slows scanning. Action granularity: Generally one action per line, although the nested exec/compile/read expression combines several operations. Reading flow: Method boundaries and consistent formatting support navigation, but inverted conditions, double negatives, and empty pass branches repeatedly interrupt otherwise straightforward logic.
Run 3
Code Structure: A cohesive configuration class with logically separated loading and filtering methods. Nesting: Mostly moderate, but unnecessary if/pass/else branches add indentation throughout. Clarity of intent: Descriptive method names, type annotations, comments, and detailed docstrings explain purpose well; repeated double negatives and abbreviated variables obscure implementation details. Code length: Functional methods are reasonably short, but redundant branches inflate the code, and extensive documentation slows scanning. Action granularity: Generally one action per line, although the nested exec/compile/read expression combines several operations. Reading flow: Method organization is natural, but inverted conditions and empty pass branches repeatedly interrupt straightforward control flow. Overall, the code is understandable but would be substantially clearer with direct conditions and guard clauses.