U Zj9@sjddlZddlZddlZddlZddlmZddlmZejddkrRe Z e fZ n e Z e efZ ddZdS)N)errors)utilc Cs|sdSt|tr tj|}n tjd}tj|sFtd|zt ||j }WnBt k rt d}tdtd||jj|fYnXd}|rD|D]\}}t|jd|rt|jd||qt|j|rt|j||qt||rt|||q||kr,t|j||qd t|} t| qzt|j|Wn(tk r|jjd |YnXt|jjt t!frt"|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)Zlong_description_content_typeZ project_urlsZprovides_extrasset_zUnknown distribution option: %s)# isinstance string_typeospathabspathexistsrDistutilsFileErrorrZ cfg_to_args script_args Exceptionsysexc_infologging exceptionDistutilsSetupError __class____name__itemshasattrmetadatagetattrsetattrreprwarningswarnsuperfinalize_options TypeError __bases__version integer_typesfloatstr) distattrvaluer attrseZ_DISTUTILS_UNSUPPORTED_METADATAkeyvalmsgr0K/var/www/html/TRUCKING_PROJECT/venv/lib/python3.8/site-packages/pbr/core.pypbr@sH           r2)rr rr distutilsrr2r version_infor'r intr% basestringlongr0r0r0r1.s