Gecko [ lorencats.com ]

Name	Size	Permission
__pycache__	[ DIR ]	drwxr-xr-x
cli	[ DIR ]	drwxr-xr-x
commands	[ DIR ]	drwxr-xr-x
models	[ DIR ]	drwxr-xr-x
operations	[ DIR ]	drwxr-xr-x
req	[ DIR ]	drwxr-xr-x
utils	[ DIR ]	drwxr-xr-x
vcs	[ DIR ]	drwxr-xr-x
__init__.py	2.8 KB	-rw-r--r--
build_env.py	4.68 KB	-rw-r--r--
cache.py	6.67 KB	-rw-r--r--
configuration.py	12.93 KB	-rw-r--r--
download.py	32.52 KB	-rw-r--r--
exceptions.py	8.69 KB	-rw-r--r--
index.py	33.98 KB	-rw-r--r--
locations.py	6.16 KB	-rw-r--r--
pep425tags.py	10.59 KB	-rw-r--r--
pyproject.py	5.35 KB	-rw-r--r--
resolve.py	13.26 KB	-rw-r--r--
wheel.py	31.26 KB	-rw-r--r--

Code Editor : pyproject.py

from __future__ import absolute_import

import io
import os

from pip._vendor import pytoml, six

from pip._internal.exceptions import InstallationError

def _is_list_of_str(obj):
    return (
        isinstance(obj, list) and
        all(isinstance(item, six.string_types) for item in obj)
    )

def load_pyproject_toml(use_pep517, pyproject_toml, setup_py, req_name):
    """Load the pyproject.toml file.

Parameters:
        use_pep517 - Has the user requested PEP 517 processing? None
                     means the user hasn't explicitly specified.
        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
        )
    """
    has_pyproject = os.path.isfile(pyproject_toml)
    has_setup = os.path.isfile(setup_py)

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

# The following cases must use PEP 517
    # We check for use_pep517 equalling False because that
    # means the user explicitly requested --no-use-pep517
    if has_pyproject and not has_setup:
        if use_pep517 is False:
            raise InstallationError(
                "Disabling PEP 517 processing is invalid: "
                "project does not have a setup.py"
            )
        use_pep517 = True
    elif build_system and "build-backend" in build_system:
        if use_pep517 is False:
            raise InstallationError(
                "Disabling PEP 517 processing is invalid: "
                "project specifies a build backend of {} "
                "in pyproject.toml".format(
                    build_system["build-backend"]
                )
            )
        use_pep517 = True

# If we haven't worked out whether to use PEP 517 yet,
    # and the user hasn't explicitly stated a preference,
    # we do so if the project has a pyproject.toml file.
    elif use_pep517 is None:
        use_pep517 = has_pyproject

# At this point, we know whether we're going to use PEP 517.
    assert use_pep517 is not None

# If we're using the legacy code path, there is nothing further
    # for us to do here.
    if not use_pep517:
        return None

if build_system is None:
        # Either the user has a pyproject.toml with no build-system
        # section, or the user has no pyproject.toml, but has opted in
        # explicitly via --use-pep517.
        # In the absence of any explicit backend specification, we
        # assume the setuptools backend, and require wheel and a version
        # of setuptools that supports that backend.
        build_system = {
            "requires": ["setuptools>=38.2.5", "wheel"],
            "build-backend": "setuptools.build_meta",
        }

# If we're using PEP 517, we have build system information (either
    # from pyproject.toml, or defaulted by the code above).
    # Note that at this point, we do not know if the user has actually
    # specified a backend, though.
    assert build_system is not None

# Ensure that the build-system section in pyproject.toml conforms
    # to PEP 518.
    error_template = (
        "{package} has a pyproject.toml file that does not comply "
        "with PEP 518: {reason}"
    )

# Specifying the build-system table but not the requires key is invalid
    if "requires" not in build_system:
        raise InstallationError(
            error_template.format(package=req_name, reason=(
                "it has a 'build-system' table but not "
                "'build-system.requires' which is mandatory in the table"
            ))
        )

# Error out if requires is not a list of strings
    requires = build_system["requires"]
    if not _is_list_of_str(requires):
        raise InstallationError(error_template.format(
            package=req_name,
            reason="'build-system.requires' is not a list of strings.",
        ))

backend = build_system.get("build-backend")
    check = []
    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, or wheel
        # (which is neede by the backend) in their requirements. So we
        # make a note to check that those requirements are present once
        # we have set up the environment.
        # TODO: Review this - it's quite a lot of work to check for a very
        # specific case. 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"
        check = ["setuptools>=38.2.5", "wheel"]

return (requires, backend, check)

${this.title}

Code Editor : pyproject.py