Name	Size	Mode	Actions
app.cpython-36.pyc	62838	0644	editdlrm
blueprints.cpython-36.pyc	21895	0644	editdlrm
cli.cpython-36.pyc	26882	0644	editdlrm
config.cpython-36.pyc	11562	0644	editdlrm
ctx.cpython-36.pyc	15441	0644	editdlrm
debughelpers.cpython-36.pyc	6377	0644	editdlrm
globals.cpython-36.pyc	1742	0644	editdlrm
helpers.cpython-36.pyc	27004	0644	editdlrm
logging.cpython-36.pyc	2400	0644	editdlrm
scaffold.cpython-36.pyc	24745	0644	editdlrm
sessions.cpython-36.pyc	13544	0644	editdlrm
signals.cpython-36.pyc	2332	0644	editdlrm
templating.cpython-36.pyc	5449	0644	editdlrm
testing.cpython-36.pyc	9089	0644	editdlrm
typing.cpython-36.pyc	1363	0644	editdlrm
views.cpython-36.pyc	4910	0644	editdlrm
wrappers.cpython-36.pyc	4901	0644	editdlrm
__init__.cpython-36.pyc	1839	0644	editdlrm
__main__.cpython-36.pyc	170	0644	editdlrm

3 ^TBg,�@sNdd
lZdd
l
Z
dd
lZdd
lZddlmZ
Gdd�d�ZGdd�de�Z d
S)�N)
� import_stringc@s\eZ
dZd
Zdeejejdd�dd�Zd ej ej ej d�dd�Z ej ej dd �d d�ZdS)�ConfigAttributez(Makes an attribute forward to the configN)�name� get_converter�returncCs|
|_||_
dS)
N)�__name__r)�selfrr�r �-/tmp/pip-build-0s3hx122/flask/flask/config.py�__init__s

zConfigAttribute.__init__)�obj�ownerrcCs0|
dkr|S|
j|j
}|jdk r,|j|�
}|S)
N)�configrr)rrr �rvr r r �__get__s





zConfigAttribute.__get__)r�valuercCs||
j|j
<dS)
N)rr)rrrr r r �__set__s
zConfigAttribute.__set__)
N)
N)r� __module__�__qualname__�__doc__�str�
t�Optional�Callabler�Anyrrr r r r r s
rc@s
eZ
dZd
Zdeejedd�dd�Zd ee e d�dd �Z d!ee e d �dd�Zeje efdd �dd�Zd"eejejejg
ejfe e d�dd�Zd#ee e d �dd�Zd$ejejeejfeje d�dd�Zd%ee e ejeejfd�dd�Zed�
dd�ZdS)&�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�defaultsrcCstj
||pi�
|
|_dS)
N)�dictrr)rrrr r r rHs

zConfig.__init__F)� variable_name�silentrcCs6tj
j|
�
}|s(|rd
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)rrr rr r r �from_envvarLs




zConfig.from_envvar)�filenamer rcCs�tj
j|j|
�}
tjd
�
}|
|_y4t|
dd��}tt |j �|
d�|j�
WdQRXWnRtk r�
}
z6|r�|j t jt jt jfkr�dSd|j�d�|_�WYdd}~XnX|j|�

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�execNFz#Unable to load configuration file (�
)T)r!�path�joinr�types� ModuleType�__file__�openr*�compile�read�__dict__�OSError�errno�ENOENT�EISDIR�ENOTDIR�strerror�from_object)rr'r �
d�config_file�
er r r r%ds




&






zConfig.from_pyfile)rrcCs>t|
t
�rt|
�
}
x&t|
�
D]}|j�rt|
|�||<qWd
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)rr�keyr r r r;�s



zConfig.from_object)r'�loadr rcCs�tj
j|j|
�}
y t|
�
�}||�
}Wd
QRXWnNtk r~
}
z2|r\|jtjtjfkr\dSd|j �d�|_ �WYd
d
}~XnX|j |�
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 toml app.config.from_file("config.toml", load=toml.load) :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. :return: ``True`` if the file was loaded successfully. .. versionadded:: 2.0 NFz#Unable to load configuration file (r+)r!r,r-rr1r5r6r7r8r:�from_mapping)rr'rDr �
frr>r r r � from_file�s





zConfig.from_filecCs6d
dl}ddl
m}
|jdtdd�
|j|
|j|d�S) aLUpdate the values in the config from a JSON file. The loaded data is passed to the :meth:`from_mapping` method. :param filename: The path to the JSON file. This can be an absolute path or relative to the config root path. :param silent: Ignore the file if it doesn't exist. :return: ``True`` if the file was loaded successfully. .. deprecated:: 2.0.0 Will be removed in Flask 2.1. Use :meth:`from_file` instead. This was removed early in 2.0.0, was added back in 2.0.1. .. versionadded:: 0.11 r
N�
)
�jsonze'from_json' is deprecated and will be removed in Flask 2.1. Use 'from_file(path, json.load)' instead.�)
� stacklevel)
r )�warnings�rI�warn�DeprecationWarningrGrD)rr'r rLrIr r r � from_json�s


zConfig.from_json)�mapping�kwargsrcKsJi}|
d
k r|j|
�

|j|�

x$|j
�D]\}}|j�r*|||<q*WdS)z�Updates the config like :meth:`update` ignoring items with non-upper keys. :return: Always returns ``True``. .. versionadded:: 0.11 NT)�update�itemsrA)rrQrRZmappingsrCrr r r rE�s 






zConfig.from_mappingT)� namespace� lowercase�trim_namespacercCsXi}xN|j�D]B\}}|j
|
�
s"q|r8|t|
�
d
�}n|}|rH|j�}|||<qW|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)rT� startswith�len�lower)rrUrVrWr�
k�
vrCr r r � get_namespace�s








zConfig.get_namespace)
rc

Csd
t|�
j
�dtj|�
�d�S)N�
<�
�
>)�typerr�__repr__)
rr r r rb&
s
zConfig.__repr__)
N)
F)
F)
F)
F)
N)TT)rrrrrrrrr�boolr&r%�Union�objectr;rZIOr�MappingrGrPrE�Dictr]rbr r r r rs**
#

)r) r6r!r.ZtypingrZwerkzeug.utilsrrrrr r r r �
s