Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/flask/__pycache__/config.cpython-39.pyc
Ðазад
a p�hD' � @ sp d Z ddlZddlZddlZddlmZ ddlmZ ddlm Z ddlm Z G dd � d e �Z G d d � d e �ZdS ) z� flask.config ~~~~~~~~~~~~ Implements the configuration related objects. :copyright: 2010 Pallets :license: BSD-3-Clause � N)� import_string� )�json)� iteritems)� string_typesc @ s, e Zd ZdZd dd�Zd dd�Zdd� ZdS ) �ConfigAttributez(Makes an attribute forward to the configNc C s || _ || _d S �N)�__name__� get_converter)�self�namer � r �|/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/flask/config.py�__init__ s zConfigAttribute.__init__c C s0 |d u r | S |j | j }| jd ur,| �|�}|S r )�configr r )r �obj�type�rvr r r �__get__ s zConfigAttribute.__get__c C s ||j | j< d S r )r r )r r �valuer r r �__set__% s zConfigAttribute.__set__)N)N)r � __module__� __qualname__�__doc__r r r r r r r r s r c @ sZ e Zd ZdZddd�Zddd�Zddd �Zd d � Zdd d �Zdd� Z ddd�Z dd� Z dS )�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 Nc C s t �| |p i � || _d S r )�dictr � root_path)r r �defaultsr r r r U s zConfig.__init__Fc C s2 t j�|�}|s$|rdS td| ��| 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: bool. ``True`` if able to load config, ``False`` otherwise. Fz�The environment variable %r is not set and as such configuration could not be loaded. Set this variable and make it point to a configuration file)�silent)�os�environ�get� RuntimeError� from_pyfile)r Z variable_namer r r r r � from_envvarY s ��zConfig.from_envvarc C s� t j�| j|�}t�d�}||_zHt|dd��(}tt |� � |d�|j � W d � n1 s\0 Y W nZ t y� } zB|r�|j t jt jt jfv r�W Y d}~dS d|j |_� W Y d}~n d}~0 0 | �|� dS ) a 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. .. versionadded:: 0.7 `silent` parameter. r �rb)�mode�execNF�&Unable to load configuration file (%s)T)r �path�joinr �types� ModuleType�__file__�openr' �compile�read�__dict__�IOError�errno�ENOENT�EISDIR�ENOTDIR�strerror� from_object)r �filenamer �d� config_file�er r r r# q s : zConfig.from_pyfilec C s: t |t�rt|�}t|�D ]}|�� rt||�| |< qdS )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)� isinstancer r �dir�isupper�getattr)r r �keyr r r r8 � s zConfig.from_objectc C s� t j�| j|�}z:t|�� }t�|�� �}W d � n1 s>0 Y W nV ty� } z>|r~|j t j t j fv r~W Y d}~dS d|j |_ � W Y d}~n d}~0 0 | � |�S )a Updates the values in the config from a JSON file. This function behaves as if the JSON object was a dictionary and passed to the :meth:`from_mapping` function. :param filename: the filename of the JSON file. 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. .. versionadded:: 0.11 NFr( )r r) r* r r. r �loadsr0 r2 r3 r4 r5 r7 � from_mapping)r r9 r Z json_filer r< r r r � from_json� s 0 zConfig.from_jsonc O s� g }t |�dkrBt|d d�r2|�|d �� � q^|�|d � n t |�dkr^tdt |� ��|�|�� � |D ]"}|D ]\}}|�� rx|| |< qxqpdS )z{Updates the config like :meth:`update` ignoring items with non-upper keys. .. versionadded:: 0.11 r r �itemsz.expected at most 1 positional argument, got %dT)�len�hasattr�appendrE � TypeErrorr? )r �mapping�kwargsZmappingsrA r r r r rC � s � zConfig.from_mappingTc C sT i }t | �D ]B\}}|�|�s q |r6|t|�d� }n|}|rF|�� }|||< q |S )ai 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 N)r � startswithrF �lower)r � namespaceZ lowercaseZtrim_namespacer �k�vrA r r r � get_namespace� s zConfig.get_namespacec C s d| j jt�| �f S )Nz<%s %s>)� __class__r r �__repr__)r r r r rS s zConfig.__repr__)N)F)F)F)TT) r r r r r r$ r# r8 rD rC rQ rS r r r r r ) s + & )r )r r3 r r+ Zwerkzeug.utilsr � r �_compatr r �objectr r r r r r r �<module> s
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка