o jl@s$UddlmZddlZddlZddlZddlZddlmZddlm Z m Z ddl m Z m Z ddlmZddlmZmZmZeeZeeZeed dZd ed <d*ddZd+ddZd+ddZd+ddZ gdZ!e"ddurve!#d     d,d-d"d#Z$d+d$d%Z%d+d&d'Z&d+d(d)Z'dS).) annotationsN)Callable)InvalidSchemeCombinationUserInstallationInvalid) SCHEME_KEYSScheme)running_under_virtualenv) change_rootget_major_minor_versionis_osx_frameworkget_preferred_schemezCallable[[str], str] | None_PREFERRED_SCHEME_APIreturnboolcCsdtvo t o tS)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/kodo/Anonymous/send/lib/python3.10/site-packages/pip/_internal/locations/_sysconfig.py _should_use_osx_framework_prefix!s rstrcCsvtrtdStr dStjjdtj}|tvr|Stjjtvr%tjjStjd}|tvr1|Stjtvr9tjSdS)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)rrsysimplementationnameosr)implementation_suffixedsuffixedrrr _infer_prefix;s   r!cCsHtrtdStrtsd}ntjd}|tvr|Sdtvr"tdS)z3Try to find a user scheme for the current platform.userosx_framework_user_user posix_user)rr rrrrrr rrr _infer_userZs  r'cCs(trtdStjd}|tvr|SdS)z,Try to find a home for the current platform.home_home posix_home)rrrrr&rrr _infer_homeis  r+)installed_basebaseinstalled_platbaseplatbaser exec_prefixuserbaseF dist_namer"r( str | Nonerootisolatedrrcsd|r r tddrrtdddurt}n |r t}nt}dur-|dkr-d}dur;fddtD}ndurIfd dtD}ni}tj||d }trx|r_|d t j } n|d t j } d t } t j | dd| |d<n|s|d}t|d|dt j |d||d|dd} |duri} tD] } t|t| | | | <qtdi| } | 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--homeNrrci|]}|qSrr.0k)r(rr zget_scheme..cr6rrr7)rrrr:r;)schemevarsr1r-pythonincludesiteUNKNOWNplatlibpurelibscriptsdata)rBrCheadersrDrEr)rr+r'r! _HOME_KEYS sysconfig get_pathsrgetrrr rpathjoinrrr getattr)r2r"r(r4r5r scheme_name variablespathsr- python_xyr<converted_keyskeyr)r(rr get_schemesL   rTcCs4tjdddkrtjdddkrdStdS)Ndarwinz/System/Library/z/usr/local/binrD)rplatformrrHrIrrrrget_bin_prefixs$ rYcC tdS)NrCrHrIrrrr get_purelib r\cCrZ)NrBr[rrrr get_platlibr]r^)rr)rr)FNNFN)r2rr"rr(r3r4r3r5rrr3rr)( __future__rloggingrrrHcollections.abcrpip._internal.exceptionsrrpip._internal.models.schemerrpip._internal.utils.virtualenvrr-r r r getLogger__name__loggersetget_scheme_namesrrMr__annotations__rr!r'r+rGget_config_varappendrTrYr\r^rrrrs>           N