Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/botocore/__pycache__/loaders.cpython-39.pyc
Ðазад
a p�h�C � @ s� d Z ddlZddlZddlmZ ddlmZ ddlmZ ddlm Z m Z ddl m Z e� e�Zdd � ZG d d � d e�Zdd d �ZG dd� de�ZG dd� de�ZdS )a� Module for loading various model files. This module provides the classes that are used to load models used by botocore. This can include: * Service models (e.g. the model for EC2, S3, DynamoDB, etc.) * Service model extras which customize the service models * Other models associated with a service (pagination, waiters) * Non service-specific config (Endpoint data, retry config) Loading a module is broken down into several steps: * Determining the path to load * Search the data_path for files to load * The mechanics of loading the file * Searching for extras and applying them to the loaded file The last item is used so that other faster loading mechanism besides the default JSON loader can be used. The Search Path =============== Similar to how the PATH environment variable is to finding executables and the PYTHONPATH environment variable is to finding python modules to import, the botocore loaders have the concept of a data path exposed through AWS_DATA_PATH. This enables end users to provide additional search paths where we will attempt to load models outside of the models we ship with botocore. When you create a ``Loader``, there are two paths automatically added to the model search path: * <botocore root>/data/ * ~/.aws/models The first value is the path where all the model files shipped with botocore are located. The second path is so that users can just drop new model files in ``~/.aws/models`` without having to mess around with the AWS_DATA_PATH. The AWS_DATA_PATH using the platform specific path separator to separate entries (typically ``:`` on linux and ``;`` on windows). Directory Layout ================ The Loader expects a particular directory layout. In order for any directory specified in AWS_DATA_PATH to be considered, it must have this structure for service models:: <root> | |-- servicename1 | |-- 2012-10-25 | |-- service-2.json |-- ec2 | |-- 2014-01-01 | | |-- paginators-1.json | | |-- service-2.json | | |-- waiters-2.json | |-- 2015-03-01 | |-- paginators-1.json | |-- service-2.json | |-- waiters-2.json | |-- service-2.sdk-extras.json That is: * The root directory contains sub directories that are the name of the services. * Within each service directory, there's a sub directory for each available API version. * Within each API version, there are model specific files, including (but not limited to): service-2.json, waiters-2.json, paginators-1.json The ``-1`` and ``-2`` suffix at the end of the model files denote which version schema is used within the model. Even though this information is available in the ``version`` key within the model, this version is also part of the filename so that code does not need to load the JSON model in order to determine which version to use. The ``sdk-extras`` and similar files represent extra data that needs to be applied to the model after it is loaded. Data in these files might represent information that doesn't quite fit in the original models, but is still needed for the sdk. For instance, additional operation parameters might be added here which don't represent the actual service api. � N)� BOTOCORE_ROOT)�json)� OrderedDict)�DataNotFoundError�UnknownServiceError�� deep_mergec s � fdd�}|S )a Cache the result of a method on a per instance basis. This is not a general purpose caching decorator. In order for this to be used, it must be used on methods on an instance, and that instance *must* provide a ``self._cache`` dictionary. c s^ � j f| }t|�� �D ] }||7 }q|| jv r:| j| S � | g|�R i |��}|| j|< |S �N)�__name__�sorted�items�_cache)�self�args�kwargs�key�pair�data��func� ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/botocore/loaders.py�_wrapper~ s z instance_cache.<locals>._wrapperr )r r r r r �instance_cacheu s r c @ s e Zd ZdZdd� Zdd� ZdS )�JSONFileLoaderzeLoader JSON files. This class can load the default format of models, which is a JSON file. c C s t j�|d �S )z�Checks if the file exists. :type file_path: str :param file_path: The full path to the file to load without the '.json' extension. :return: True if file path exists, False otherwise. �.json)�os�path�isfile)r � file_pathr r r �exists� s zJSONFileLoader.existsc C sn |d }t j�|�sdS t|d��8}|�� �d�}t�d|� tj |t d�W d � S 1 s`0 Y dS )z�Attempt to load the file path. :type file_path: str :param file_path: The full path to the file to load without the '.json' extension. :return: The loaded data if it exists, otherwise None. r N�rbzutf-8zLoading JSON file: %s)�object_pairs_hook) r r r �open�read�decode�logger�debugr �loadsr )r r � full_path�fp�payloadr r r � load_file� s zJSONFileLoader.load_fileN)r � __module__� __qualname__�__doc__r r, r r r r r � s r c C sP | du rt � S g }| �tj�}|D ]"}tj�tj�|��}|�|� q"t |d�S )a� Create a Loader class. This factory function creates a loader given a search string path. :type search_string_path: str :param search_string_path: The AWS_DATA_PATH value. A string of data path values separated by the ``os.path.pathsep`` value, which is typically ``:`` on POSIX platforms and ``;`` on windows. :return: A ``Loader`` instance. N)�extra_search_paths)�Loader�splitr �pathsepr � expanduser� expandvars�append)Zsearch_path_string�pathsZ extra_pathsr r r r � create_loader� s r8 c @ s� e Zd ZdZeZej�e d�Z ej�ej� d�dd�Z dgZ d d d �Zed d � �Zed d� �Zedd� �Zedd� �Zedd� �Zed dd��Zdd� Zedd� �Zd d d �ZdS )!r1 z�Find and load data models. This class will handle searching for and loading data models. The main method used here is ``load_service_model``, which is a convenience method over ``load_data`` and ``determine_latest_version``. r �~z.aws�modelsZsdkNTc C sn i | _ |d u r| �� }|| _|d ur,|| _ng | _|rJ| j�| j| jg� g | _|rb| j�| j� t � | _ d S r ) r �FILE_LOADER_CLASS� file_loader� _search_paths�extend�CUSTOMER_DATA_PATH�BUILTIN_DATA_PATH� _extras_types�BUILTIN_EXTRAS_TYPES�ExtrasProcessor�_extras_processor)r r0 r< �cacheZ include_default_search_pathsZinclude_default_extrasr r r �__init__� s �zLoader.__init__c C s | j S r )r= �r r r r � search_paths� s zLoader.search_pathsc C s | j S r )rA rG r r r � extras_types� s zLoader.extras_typesc s� t � }| �� D ]r� � fdd�t�� �D �}|D ]P}tj�� |�}t�|�}|D ].}tj�|||�}| j�|�rN|�|� q.qNq.qt |�S )ap List all known services. This will traverse the search path and look for all known services. :type type_name: str :param type_name: The type of the service (service-2, paginators-1, waiters-2, etc). This is needed because the list of available services depends on the service type. For example, the latest API version available for a resource-1.json file may not be the latest API version available for a services-2.json file. :return: A list of all services. The list of services will be sorted. c s& g | ] }t j�t j�� |��r|�qS r )r r �isdir�join)�.0�d�� possible_pathr r � <listcomp> s �z2Loader.list_available_services.<locals>.<listcomp>) �set�_potential_locationsr �listdirr rK r< r �addr ) r � type_nameZservicesZpossible_services� service_nameZ full_dirnameZ api_versions� api_versionZfull_load_pathr rN r �list_available_services� s" � � z Loader.list_available_servicesc C s t | �||��S )a Find the latest API version available for a service. :type service_name: str :param service_name: The name of the service. :type type_name: str :param type_name: The type of the service (service-2, paginators-1, waiters-2, etc). This is needed because the latest API version available can depend on the service type. For example, the latest API version available for a resource-1.json file may not be the latest API version available for a services-2.json file. :rtype: str :return: The latest API version. If the service does not exist or does not have any available API data, then a ``DataNotFoundError`` exception will be raised. )�max�list_api_versions)r rV rU r r r �determine_latest_version! s z Loader.determine_latest_versionc C sh t � }| j|ddd�D ]:}t�|�D ]*}tj�|||�}| j�|�r$|�|� q$q|s`t |d��t |�S )ay List all API versions available for a particular service type :type service_name: str :param service_name: The name of the service :type type_name: str :param type_name: The type name for the service (i.e service-2, paginators-1, etc.) :rtype: list :return: A list of API version strings in sorted order. T)� must_exist�is_dir�Z data_path) rQ rR r rS r rK r< r rT r r )r rV rU Zknown_api_versionsrO �dirnamer) r r r rZ 8 s � zLoader.list_api_versionsc C sv | � |�}||vr(t|d�t|��d��|du r<| �||�}tj�|||�}| �|�}| �|||�}| j � ||� |S )aJ Load a botocore service model This is the main method for loading botocore models (e.g. a service model, pagination configs, waiter configs, etc.). :type service_name: str :param service_name: The name of the service (e.g ``ec2``, ``s3``). :type type_name: str :param type_name: The model type. Valid types include, but are not limited to: ``service-2``, ``paginators-1``, ``waiters-2``. :type api_version: str :param api_version: The API version to load. If this is not provided, then the latest API version will be used. :type load_extras: bool :param load_extras: Whether or not to load the tool extras which contain additional data to be added to the model. :raises: UnknownServiceError if there is no known service with the provided service_name. :raises: DataNotFoundError if no data could be found for the service_name/type_name/api_version. :return: The loaded data, as a python type (e.g. dict, list, etc). z, )rV Zknown_service_namesN) rX r rK r r[ r r � load_data� _find_extrasrD �process)r rV rU rW Zknown_servicesr) �modelZ extras_datar r r �load_service_modelV s �� zLoader.load_service_modelc c sP | j D ]D}d||f }tj�|||�}z| �|�V W q tyH Y q0 qdS )z-Creates an iterator over all the extras data.z %s.%s-extrasN)rI r r rK r` r )r rV rU rW Z extras_typeZ extras_namer) r r r ra � s zLoader._find_extrasc C s: | � |�D ] }| j�|�}|dur | S q t|d��dS )a0 Load data given a data path. This is a low level method that will search through the various search paths until it's able to load a value. This is typically only needed to load *non* model files (such as _endpoints and _retry). If you need to load model files, you should prefer ``load_service_model``. :type name: str :param name: The data path, i.e ``ec2/2015-03-01/service-2``. :return: The loaded data. If no data could be found then a DataNotFoundError is raised. Nr^ )rR r< r, r )r �namerO �foundr r r r` � s zLoader.load_dataFc c sl | j D ]`}tj�|�r|}|d ur0tj�||�}|s<|V q|rTtj�|�rT|V qtj�|�r|V qd S r )rH r r rJ rK r )r re r\ r] r r) r r r rR � s zLoader._potential_locations)NNNTT)N)NFF)r r- r. r/ r r; r r rK r r@ r4 r? rB rF �propertyrH rI r rX r[ rZ rd ra r` rR r r r r r1 � s: � � ( 0 �r1 c @ s e Zd ZdZdd� Zdd� ZdS )rC z5Processes data from extras files into service models.c C s |D ]}| � ||� qdS )a$ Processes data from a list of loaded extras files into a model :type original_model: dict :param original_model: The service model to load all the extras into. :type extra_models: iterable of dict :param extra_models: A list of loaded extras models. N)�_process)r Zoriginal_modelZ extra_models�extrasr r r rb � s zExtrasProcessor.processc C s d|v rt ||d � dS )z3Process a single extras model into a service model.�mergeNr )r rc Z extra_modelr r r rh � s zExtrasProcessor._processN)r r- r. r/ rb rh r r r r rC � s rC )N)r/ r �loggingZbotocorer Zbotocore.compatr r Zbotocore.exceptionsr r Zbotocore.utilsr � getLoggerr r& r �objectr r8 r1 rC r r r r �<module> s [ ( s
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка