a s h$ @s0ddlmZddlZddlZddlZddlZddlmZmZddl m Z m Z ddl m Z ddlmZmZmZeeZeeZeeddZd d d d Zd d ddZd d ddZd d ddZgdZeddure dd"d d ddd dddddZ!d d ddZ"d d ddZ#d d d d!Z$dS)#) annotationsN)InvalidSchemeCombinationUserInstallationInvalid) SCHEME_KEYSScheme)running_under_virtualenv) change_rootget_major_minor_versionis_osx_frameworkZget_preferred_schemebool)returncCsdtvot otS)aCheck for Apple's ``osx_framework_library`` scheme. Python distributed by Apple's Command Line Tools has this special scheme that's used when: * This is a framework build. * We are installing into the system prefix. This does not account for ``pip install --prefix`` (also means we're not installing to the system prefix), which should use ``posix_prefix``, but logic here means ``_infer_prefix()`` outputs ``osx_framework_library``. But since ``prefix`` is not available for ``sysconfig.get_default_scheme()``, which is the stdlib replacement for ``_infer_prefix()``, presumably Apple wouldn't be able to magically switch between ``osx_framework_library`` and ``posix_prefix``. ``_infer_prefix()`` returning ``osx_framework_library`` means its behavior is consistent whether we use the stdlib implementation or our own, and we deal with this special case in ``get_scheme()`` instead. osx_framework_library)_AVAILABLE_SCHEMESrr rr^/var/www/html/assistant/venv/lib/python3.9/site-packages/pip/_internal/locations/_sysconfig.py _should_use_osx_framework_prefixs rstrcCsvtr tdStrdStjjdtj}|tvr6|StjjtvrJtjjStjd}|tvrb|StjtvrrtjSdS)a!Try to find a prefix scheme for the current platform. This tries: * A special ``osx_framework_library`` for Python distributed by Apple's Command Line Tools, when not running in a virtual environment. * Implementation + OS, used by PyPy on Windows (``pypy_nt``). * Implementation without OS, used by PyPy on POSIX (``pypy``). * OS + "prefix", used by CPython on POSIX (``posix_prefix``). * Just the OS name, used by CPython on Windows (``nt``). If none of the above works, fall back to ``posix_prefix``. prefixr__prefix posix_prefix)_PREFERRED_SCHEME_APIrsysimplementationnameosr)Zimplementation_suffixedsuffixedrrr _infer_prefix8s   rcCsHtr tdStrtsd}n tjd}|tvr6|SdtvrDtdS)z3Try to find a user scheme for the current platform.userosx_framework_user_user posix_user)rr rrrrrrrrr _infer_userWs  r$cCs(tr tdStjd}|tvr$|SdS)z,Try to find a home for the current platform.home_home posix_home)rrrrr#rrr _infer_homefs  r()installed_basebaseinstalled_platbaseplatbaser exec_prefixuserbaseFz str | Noner) dist_namerr%rootisolatedrr csh|rrtddr$r$tdddur4t}n|r@t}nt}durZ|dkrZd}durvfddtD}n durfd dtD}ni}tj||d }tr|r|d t j } n|d t j } d t } t j | dd| |d<n|sd}t|d|dt j |d||d|dd} |durdi} tD]} t|t| | | | <q:tfi| } | S)a\ Get the "scheme" corresponding to the input parameters. :param dist_name: the name of the package to retrieve the scheme for, used in the headers scheme path :param user: indicates to use the "user" scheme :param home: indicates to use the "home" scheme :param root: root under which other directories are re-based :param isolated: ignored, but kept for distutils compatibility (where this controls whether the user-site pydistutils.cfg is honored) :param prefix: indicates to use the "prefix" scheme and provides the base directory for the same z--userz--prefixz--homeNrrcsi|] }|qSrr.0k)r%rr zget_scheme..csi|] }|qSrrr2)rrrr5r6)schemevarsr.r*pythonincludesiteUNKNOWNplatlibpurelibscriptsdata)r=r>headersr?r@)rr(r$r _HOME_KEYS sysconfig get_pathsrgetrrr rpathjoinrrr getattr)r/rr%r0r1rZ scheme_name variablespathsr*Z python_xyr7Zconverted_keyskeyr)r%rr get_scheme}sL    rLcCs4tjdddkr(tjdddkr(dStdS)Ndarwinz/System/Library/z/usr/local/binr?)rplatformrrCrDrrrrget_bin_prefixs$rQcCs tdS)Nr>rCrDrrrr get_purelibsrScCs tdS)Nr=rRrrrr get_platlibsrT)FNNFN)% __future__rloggingrrrCpip._internal.exceptionsrrpip._internal.models.schemerrpip._internal.utils.virtualenvrr*r r r getLogger__name__loggersetget_scheme_namesrrHrrrr$r(rBget_config_varappendrLrQrSrTrrrrs6      N