o

'we82�@
sbdd
lm
Z

ddlZddlZddlZddlZddlZddlm	Z	
Gdd�d�Z
Gdd�de�ZdS)�)
�annotationsN)
�
import_stringc@
s2eZ
dZd
Zddd	d
�Zdddd�Zddd�ZdS)�ConfigAttributez(Makes an attribute forward to the configN�name�str�
get_converter�t.Callable | None�return�NonecC
s|
|_||_
dS�
N)�__name__r)�selfrr�r�E/home/arjun/projects/env/lib/python3.10/site-packages/flask/config.py�__init__s


zConfigAttribute.__init__�obj�t.Any�ownercC
s0|
dur|S|
j|j
}|jdu
r|�|�
}|Sr)�configrr)r
rr�rvrrr�__get__s







zConfigAttribute.__get__�valuecC
s||
j|j
<dSr)rr)r
rrrrr�__set__s
zConfigAttribute.__set__r)rrrrr	r
)rrrrr	r)rrrrr	r
)r�
__module__�__qualname__�__doc__rrrrrrrrs

rc
s�eZ
dZd
Z	d4d5�f
d	d
�
Zd6d7dd�Z	d8ejd�
d9dd�Zd6d:dd�Z	d;dd�Z
		 d<d=d$d%�Z	d4d>d*d+�Z	 d?d@d0d1�Z
dAd2d3�Z�ZS)B�Configa�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
    N�	root_path�str | os.PathLike�defaults�dict | Noner	r
c
st��
|pi�

|
|_dSr)�superrr)r
rr�
�	__class__rrrKs

zConfig.__init__F�
variable_namer�silent�boolcC
s6tj
�|
�
}|s|rd
Std|
�d��
�
|j||d�S)a�
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.
        FzThe environment variable zv is not set and as such configuration could not be loaded. Set this variable and make it point to a configuration file)
r%)�os�environ�get�RuntimeError�from_pyfile)r
r$r%rrrr�from_envvarQs





�zConfig.from_envvar�FLASK)
�loads�prefixr.�t.Callable[[str], t.Any]c

	C
s�|
�d
�}
t|
�
}t
tj�
D]K}|�|
�
sqtj|}z||�
}Wn	ty*


Yn
w||d�}d|v
r:|||<q|}|�d�
�
^}}|D]}	|	|v
rPi||	<||	}qF|||<qdS)aLoad 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
        �
_N�__T)�len�sortedr'r(�
startswith�	Exception�split)
r
r/r.�
len_prefix�keyr�current�parts�tail�partrrr�from_prefixed_envis.







�




zConfig.from_prefixed_env�filenamec
C
s�tj
�|j|
�}
t�d
�
}|
|_z$t|
dd��}tt	|�
�|
d�|j�
Wd�
n1s.w



Y
Wn)ty]
}
z|rP|j
t
jt
jt
jfvrPWYd}~dSd|j�d�|_�d}~w
w|�|�

d	S)
aTUpdates 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.
        r�rb)
�mode�execNF�#Unable to load configuration file (�
)T)r'�path�joinr�types�
ModuleType�__file__�openrB�compile�read�__dict__�OSError�errno�ENOENT�EISDIR�ENOTDIR�strerror�from_object)r
r?r%�
d�config_file�
errrr+�s"





��



��

zConfig.from_pyfiler�object | strcC
s:t|
t
�r	t|
�
}
t|
�
D]
}|��rt|
|�||<q
d
S)a�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
        N)�
isinstancerr�dir�isupper�getattr)r
rr9rrrrT�s
 



��zConfig.from_objectT�load�$t.Callable[[t.IO[t.Any]], t.Mapping]�textc
C
s�tj
�|j|
�}
zt|
|rd
n
d��}||�
}Wd�
n1s!w



Y
Wn'tyN
}
z|rA|jtjtjfvrAWYd}~dSd|j	�d�|_	�d}~w
w|�
|�
S)a"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
        �
rr@NFrCrD)r'rErFrrJrNrOrPrQrS�from_mapping)r
r?r]r%r_�
frrWrrr�	from_file�s"


��


��
zConfig.from_file�mapping�t.Mapping[str, t.Any] | None�kwargsrcK
sFi}|
d
u
r|�|
�

|�|�

|�
�D]\}}|��r |||<qdS)z�Updates the config like :meth:`update` ignoring items with
        non-upper keys.

        :return: Always returns ``True``.

        .. versionadded:: 0.11
        NT)�update�itemsr[)r
rdrf�mappingsr9rrrrra
s








�
zConfig.from_mapping�	namespace�	lowercase�trim_namespace�dict[str, t.Any]cC
sTi}|��D]!\}}|�
|
�
sq|r|t|
�
d
�}n|}|r#|��}|||<q|S)aiReturns 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
        N)rhr5r3�lower)r
rjrkrlr�
k�
vr9rrr�
get_namespace/
s










zConfig.get_namespacec

C
sd
t|�
j
�dt�|�
�d�S)N�
<�
 �
>)�typer�dict�__repr__)
r
rrrrwZ
s
zConfig.__repr__r)rrrr r	r
)
F)r$rr%r&r	r&)
r-)r/rr.r0r	r&)r?rr%r&r	r&)rrXr	r
)FT)
r?rr]r^r%r&r_r&r	r&)rdrerfrr	r&)TT)rjrrkr&rlr&r	rm)r	r)rrrrrr,�jsonr.r>r+rTrcrarqrw�
__classcell__rrr"rrs&
,��
�@
*
�1��+r)
�
__future__rrOrxr'rG�typing�
t�werkzeug.utilsrrrvrrrrr�<module>
s