a j@sddlmZddlZddlmZddlmZddlmZddl m Z m Z m Z ddl mZddlmZd d d d d ZdddddZedgdZdddddddZdS)) annotationsN) namedtuple)Any)InvalidRequirement)InstallationErrorInvalidPyProjectBuildRequiresMissingPyProjectBuildRequires)tomllib)get_requirementrbool)objreturncCst|totdd|DS)Ncss|]}t|tVqdS)N) isinstancestr).0itemr=E:\soccer\ml_env\Lib\site-packages\pip/_internal/pyproject.py z"_is_list_of_str..)rlistall)r rrr_is_list_of_strsrr)unpacked_source_directoryr cCstj|dS)Nzpyproject.toml)ospathjoin)rrrrmake_pyproject_pathsrBuildSystemDetails)requiresbackendcheck backend_path)pyproject_tomlsetup_pyreq_namer c CsLtj|}tj|}|s.|s.t|d|rxt|dd}t|}Wdn1sb0Y|d}nd}|durdgdd}d |vrt |d |d }t |st |d d |D]L} z t | Wqt y } z t |d | d | WYd} ~ qd} ~ 00q|d} |dg} g} | dur>d} dg} t|| | | S)aLoad the pyproject.toml file. Parameters: pyproject_toml - Location of the project's pyproject.toml file setup_py - Location of the project's setup.py file req_name - The name of the requirement we're processing (for error reporting) Returns: None if we should use the legacy code path, otherwise a tuple ( requirements from pyproject.toml, name of PEP 517 backend, requirements we should check are installed after setting up the build environment directory paths to import the backend from (backend-path), relative to the project root. ) zW does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.zutf-8)encodingNz build-systemzsetuptools>=40.8.0z setuptools.build_meta:__legacy__)r build-backendr)packagezIt is not a list of strings.)r(reasonz$It contains an invalid requirement: r'z backend-path)rrisfileropenr loadsreadgetrrrr rr)r#r$r% has_pyproject has_setupfpp_toml build_systemr requirementerrorr r"r!rrrload_pyproject_tomlsP  ,       r6) __future__rr collectionsrtypingr"pip._vendor.packaging.requirementsrpip._internal.exceptionsrrrpip._internal.utils.compatr pip._internal.utils.packagingr rrrr6rrrrs