FileMgr

✏️ /opt/cloudlinux/venv/lib/python3.11/site-packages/pip/_internal/pyproject.py

✕ Tutup

from __future__ import annotations

import os
from collections import namedtuple
from typing import Any

from pip._vendor.packaging.requirements import InvalidRequirement

from pip._internal.exceptions import (
    InstallationError,
    InvalidPyProjectBuildRequires,
    MissingPyProjectBuildRequires,
)
from pip._internal.utils.compat import tomllib
from pip._internal.utils.packaging import get_requirement

def _is_list_of_str(obj: Any) -> bool:
    return isinstance(obj, list) and all(isinstance(item, str) for item in obj)

def make_pyproject_path(unpacked_source_directory: str) -> str:
    return os.path.join(unpacked_source_directory, "pyproject.toml")

BuildSystemDetails = namedtuple(
    "BuildSystemDetails", ["requires", "backend", "check", "backend_path"]
)

def load_pyproject_toml(
    pyproject_toml: str, setup_py: str, req_name: str
) -> BuildSystemDetails:
    """Load 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.
        )
    """
    has_pyproject = os.path.isfile(pyproject_toml)
    has_setup = os.path.isfile(setup_py)

if not has_pyproject and not has_setup:
        raise InstallationError(
            f"{req_name} does not appear to be a Python project: "
            f"neither 'setup.py' nor 'pyproject.toml' found."
        )

if has_pyproject:
        with open(pyproject_toml, encoding="utf-8") as f:
            pp_toml = tomllib.loads(f.read())
        build_system = pp_toml.get("build-system")
    else:
        build_system = None

if build_system is None:
        # In the absence of any explicit backend specification, we
        # assume the setuptools backend that most closely emulates the
        # traditional direct setup.py execution, and require wheel and
        # a version of setuptools that supports that backend.

build_system = {
            "requires": ["setuptools>=40.8.0"],
            "build-backend": "setuptools.build_meta:__legacy__",
        }

# Ensure that the build-system section in pyproject.toml conforms
    # to PEP 518.

# Specifying the build-system table but not the requires key is invalid
    if "requires" not in build_system:
        raise MissingPyProjectBuildRequires(package=req_name)

# Error out if requires is not a list of strings
    requires = build_system["requires"]
    if not _is_list_of_str(requires):
        raise InvalidPyProjectBuildRequires(
            package=req_name,
            reason="It is not a list of strings.",
        )

# Each requirement must be valid as per PEP 508
    for requirement in requires:
        try:
            get_requirement(requirement)
        except InvalidRequirement as error:
            raise InvalidPyProjectBuildRequires(
                package=req_name,
                reason=f"It contains an invalid requirement: {requirement!r}",
            ) from error

backend = build_system.get("build-backend")
    backend_path = build_system.get("backend-path", [])
    check: list[str] = []
    if backend is None:
        # If the user didn't specify a backend, we assume they want to use
        # the setuptools backend. But we can't be sure they have included
        # a version of setuptools which supplies the backend. So we
        # make a note to check that this requirement is present once
        # we have set up the environment.
        # This is quite a lot of work to check for a very specific case. But
        # the problem is, that case is potentially quite common - projects that
        # adopted PEP 518 early for the ability to specify requirements to
        # execute setup.py, but never considered needing to mention the build
        # tools themselves. The original PEP 518 code had a similar check (but
        # implemented in a different way).
        backend = "setuptools.build_meta:__legacy__"
        check = ["setuptools>=40.8.0"]

return BuildSystemDetails(requires, backend, check, backend_path)

Batal

⬅ pip 23 item

Nama	Tipe	Ukuran	Diubah	Perm	Aksi
📁 __pycache__	dir	—	06/02/26 03:10	0755	📂
📁 cli	dir	—	06/02/26 03:10	0755	📂
📁 commands	dir	—	06/02/26 03:10	0755	📂
📁 distributions	dir	—	06/02/26 03:10	0755	📂
📁 index	dir	—	06/02/26 03:10	0755	📂
📁 locations	dir	—	06/02/26 03:10	0755	📂
📁 metadata	dir	—	06/02/26 03:10	0755	📂
📁 models	dir	—	06/02/26 03:10	0755	📂
📁 network	dir	—	06/02/26 03:10	0755	📂
📁 operations	dir	—	06/02/26 03:10	0755	📂
📁 req	dir	—	06/02/26 03:10	0755	📂
📁 resolution	dir	—	06/02/26 03:10	0755	📂
📁 utils	dir	—	06/02/26 03:12	0755	📂
📁 vcs	dir	—	06/02/26 03:10	0755	📂
🐍 __init__.py	py	511 B	20/01/26 19:58	0644	✏️ ⬇
🐍 build_env.py	py	13.9 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 cache.py	py	10.1 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 configuration.py	py	14.2 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 exceptions.py	py	28.9 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 main.py	py	338 B	20/01/26 19:58	0644	✏️ ⬇
🐍 pyproject.py	py	4.4 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 self_outdated_check.py	py	8.3 KB	20/01/26 19:58	0644	✏️ ⬇
🐍 wheel_builder.py	py	8.8 KB	20/01/26 19:58	0644	✏️ ⬇

✏️ Rename

🔑 Ubah Permission