Your IP : 216.73.216.224
U
jP�^9 � @ sj d dl Z d dlZd dlZd dlZd dlmZ d dlmZ ejd dkrRe Z
e fZ n e
Z
e efZ dd� ZdS )� N)�errors)�util� c
C s� |sdS t |t�r tj�|�}n tj�d�}tj�|�sFt�d| ��zt� || j
�}W nB t k
r� t �
� d }t�d� t�d||jj|f ��Y nX d}|�rD|�� D ]�\}}t| jd| �r�t| jd| �|� q�t| j|�r�t| j||� q�t| |��rt| ||� q�||k�r,t| j||� q�d t|� } t�| � q�zt| j| �� � W n( t k
�r� | jj d
� | � Y nX t | jj t t!f ��r�t"| jj �| j_ dS ) a= Implements the actual pbr setup() keyword.
When used, this should be the only keyword in your setup() aside from
`setup_requires`.
If given as a string, the value of pbr is assumed to be the relative path
to the setup.cfg file to use. Otherwise, if it evaluates to true, it
simply assumes that pbr should be used, and the default 'setup.cfg' is
used.
This works by reading the setup.cfg file, parsing out the supported
metadata and command options, and using them to rebuild the
`DistributionMetadata` object and set the newly added command options.
The reason for doing things this way is that a custom `Distribution` class
will not play nicely with setup_requires; however, this implementation may
not work well with distributions that do use a `Distribution` subclass.
Nz setup.cfgz%The setup.cfg file %s does not exist.� z
Error parsingzError parsing %s: %s: %s)Z long_description_content_typeZ project_urlsZprovides_extrasZset_z Unknown distribution option: %s���)#�
isinstance� string_type�os�path�abspath�existsr ZDistutilsFileErrorr Z cfg_to_argsZ script_args� Exception�sys�exc_info�loggingZ exceptionZDistutilsSetupError� __class__�__name__�items�hasattrZmetadata�getattr�setattr�repr�warnings�warn�superZfinalize_options� TypeError� __bases__�version�
integer_types�float�str)
Zdist�attr�valuer
Zattrs�eZ _DISTUTILS_UNSUPPORTED_METADATA�key�val�msg� r' �*/usr/lib/python3/dist-packages/pbr/core.py�pbr@ sH
�
�
r) )r r r r Z distutilsr r) r � version_infor r �intr Z
basestringZlongr' r' r' r( �<module>. s