o Ni<@s*dZddlmZddlmZddlmZddlZddlZddlZddlZddl Z ddl Z ddl m Z ddl mZddlZddlmZddlZdd lmZd Zd d d DZdZddZddZddZddZddZd*ddZd+ddZddZd d!Zd"d#Z d+d$d%Z!d&d'Z"d+d(d)Z#ej$j%Z%dS),z4 Utilities with minimum-depends for use in setup.py )absolute_import)print_function)unicode_literalsN)log)urlparse)git)version)zrequirements.txtztools/pip-requirescCsg|] }|tjdqS)r)sys version_info).0xr A/home/ubuntu/.local/lib/python3.10/site-packages/pbr/packaging.py )s r)zrequirements-py%d.txtztools/pip-requires-py%d)ztest-requirements.txtztools/test-requirescCs4tjd}|rtdd|dDStttS)NPBR_REQUIREMENTS_FILEScss|]}|VqdSNstripr fr r r 3sz)get_requirements_files..,)osenvirongettuplesplitPY_REQUIREMENTS_FILESlistREQUIREMENTS_FILES)filesr r rget_requirements_files0s  r!cCs:g}||d}|r||||d|||<dS)z5Append a separated list to possibly existing value. N)rappendextendjoin)configkey text_list new_value current_valuer r rappend_text_list<s    r,cCsdd|DS)NcSsg|] }tj|r|qSr )rpathexistsrr r rrGsz!_any_existing..r ) file_listr r r _any_existingFsr0c Cst|}dd|D}|rtd|tdd|D}|D] }t|d}|dWdS1s9wYqgS)NcSsg|]}|tvr|qSr rrr r rrOz'get_reqs_from_files..zSupport for '-pyN'-suffixed requirements files is removed in pbr 5.0 and these files are now ignored. Use environment markers instead. Conflicting files: %rcSsg|]}|tvr|qSr r1rr r rrYr2rr#)r0warningswarnDeprecationWarningopenreadr)requirements_filesexisting deprecatedrequirements_filefilr r rget_reqs_from_filesKs  &r>cCstdd|dS)Na(?P[\w.-]+)-(?P(?P(?P0|[1-9][0-9]*)\.(?P0|[1-9][0-9]*)\.(?P0|[1-9][0-9]*)){1}(?P(?:\-(?P(?:(?=[0]{1}[0-9A-Za-z-]{0})(?:[0]{1})|(?=[1-9]{1}[0-9]*[A-Za-z]{0})(?:[0-9]+)|(?=[0-9]*[A-Za-z-]+[0-9A-Za-z-]*)(?:[0-9A-Za-z-]+)){1}(?:\.(?=[0]{1}[0-9A-Za-z-]{0})(?:[0]{1})|\.(?=[1-9]{1}[0-9]*[A-Za-z]{0})(?:[0-9]+)|\.(?=[0-9]*[A-Za-z-]+[0-9A-Za-z-]*)(?:[0-9A-Za-z-]+))*){1}){0,1}(?:\+(?P(?:[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))){0,1}))z"\g>=\g)resubgroups)matchr r r egg_fragmentas  rDFc Cs0|durt}g}t|D]}|r|drq td|r q |dr6|dd}|t|g|d7}q tj j |}td|rNtd|}| d }t |}|jr^td t|j}n td |rhd}d }|durtd d|}|r|d} | dkrd} |d| }||q td||fq |S)N#z5^\s*(-i|--index-url|--extra-index-url|--find-links).*z-r ) strip_markersz\s*-e\s+z \s*-e\s+(.*)$zegg=([^&]+).*$z\s*-f\s+zIndex Locationz#.*$r";rz[pbr] Excluding %s: %s)r!r>r startswithr@rC partitionparse_requirementspbr_compat packagingextract_project_namegrouprschemerArDfragmentfindr$rinfo) r9rH requirementslinereq_file project_nameextracteggreasonsemi_posr r rrMwsH         rMcCsj|durt}g}t|D]%}td|rq td|r'|tdd|q td|r2||q |S)Nz (\s*#)|(\s*$)z \s*-[ef]\s+r"z+^\s*(https?|git(\+(https|ssh))?|svn|hg)\S*:)r!r>r@rCr$rA)r9dependency_linksrXr r rparse_dependency_linkss     r`c si|r |d}nd}tdd|g|}t}d}|dD])}|}||s0q|t|dd}|d d |Dqfd d }|d |d|d|d|d|d|d|d|D] } t d| qh ddS)aCalculate the sort of semver increment needed from git history. Every commit from HEAD to tag is consider for Sem-Ver metadata lines. See the pbr docs for their syntax. :return: a dict of kwargs for passing into SemanticVersion.increment. z..HEADHEADrz --pretty=%Bzsem-ver:r#NrcSsg|]}|qSr r)r symbolr r rrsz)_get_increment_kwargs..cs"||vrd|<||dSdS)NT)discard)rbsymbolsimpactresultr r_handle_symbolsz-_get_increment_kwargs.._handle_symbolbugfixpatchfeatureminor deprecationz api-breakmajorz[pbr] Unknown Sem-Ver symbol %r) r_run_git_commandsetrlowerrrKlenupdaterrVpop) git_dirtag version_spec changelogrdheaderrX new_symbolsrhrbr rfr_get_increment_kwargss0         r{c Cstj|d}d}t|D]9\}\}}}t}i}t|D]}ztj|}|||<||Wqt y8Yqw|rE|t ||fSq d|fS)zReturn the commit data about the most recent tag. We use git-describe to find this out, but if there are no tags then we fall back to counting commits since the beginning of time. )rurr") r_iter_log_oneline enumeraterprrSemanticVersionfrom_pip_stringadd Exceptionmax) rurx row_countignoredtag_set version_tags semver_to_tagrvsemverr r r_get_revno_and_last_tags"    rcCst|\}}tj|p d}|dkr|}n |jdit||}|dur1||kr1td||d|dkr7|S||}|durK||}||krK|S|S)aCalculate a version from a target version in git_dir. This is used for untagged versions only. A new version is calculated as necessary based on git metadata - distance to tags, current hash, contents of commit messages. :param git_dir: The git directory we're working from. :param target_version: If None, the last tagged version (or 0 if there are no tags yet) is incremented as needed to produce an appropriate target version following semver rules. Otherwise target_version is used as a constraint - if semver rules would result in a newer version then an exception is raised. :return: A semver version object. 0rNzRgit history requires a target version of %(new)s, but target version is %(target)s)newtargetr )rrr~r incrementr{ ValueErrorto_dev)rutarget_versionrvdistance last_semver new_versionnew_dev target_devr r r_get_version_from_git_targets*   rcCst}|r:ztjddg|dddd}tj|}Wnty0|r,tj|}nd}Ynwt||}| Szt WSt yHYdSw) aCalculate a version string from git. If the revision is tagged, return that. Otherwise calculate a semantic version description of the tree. The number of revisions since the last tag is included in the dev counter in the version for untagged versions. :param pre_version: If supplied use this as the target version rather than inferring one from the last tag + commit messages. describez --exact-matchT)throw_on_error-.Nr") r_run_git_functionsroreplacerr~rrrrelease_stringunicode NameError) pre_versionrutaggedrrgr r r_get_version_from_git:s0     rc Csddg}i}|D],}zt|d }t|}Wdn1s wYWqtttjjfy4Yqw|dd|kr?dS|ddS)zGet the version from package metadata if present. This looks for PKG-INFO if present (for sdists), and if not looks for METADATA (for wheels) and failing that will return None. zPKG-INFOMETADATAr3NNameVersion)r7emailmessage_from_fileIOErrorOSErrorerrors MessageErrorr) package_namepkg_metadata_filenames pkg_metadatafilenamepkg_metadata_filer r r_get_version_from_pkg_metadataas   rcCshtjdtjdd}|r|St|}|r|St|}tjddkr(|d}|r,|Stdj |d) a Get the version of the project. First, try getting it from PKG-INFO or METADATA, if it exists. If it does, that means we're in a distribution tarball or that install has happened. Otherwise, if there is no PKG-INFO or METADATA file, pull the version from git. We do not support setup.py version sanity in git archive tarballs, nor do we support packagers directly sucking our git repo into theirs. We expect that a source tarball be made from our git repo - or that if someone wants to make a source tarball from a fork of our repo with additional tags in it that they understand and desire the results of doing that. :param pre_version: The version field from setup.cfg - if set then this version will be the next release. PBR_VERSIONOSLO_PACKAGE_VERSIONNrrGzutf-8a(Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name {name} was given, but was not able to be found.)name) rrrrrr r encoderformat)rrrr r r get_versionvs$ r)NFr)&__doc__ __future__rrrr email.errorsrr@r r4 distutilsrpbr._compat.fiverpbr._compat.packagingrNr pbr.pbr_jsonrrrTEST_REQUIREMENTS_FILESr!r,r0r>rDrMr`r{rrrrrpbr_jsonwrite_pbr_jsonr r r rsF           @. ''  0