File: //lib/python3.8/site-packages/setuptools/__pycache__/build_meta.cpython-38.opt-1.pyc
U
Qab}% @ s d Z ddlZddlZddlZddlZddlZddlZddlZddlZddl m
Z
ddlmZ ddl
mZ dddd d
ddgZG d
d deZG dd dejjZdd Zdd Zdd Zdd ZG dd deZG dd deZe ZejZejZejZejZej Z e Z!dS )a- A PEP 517 interface to setuptools
Previously, when a user or a command line tool (let's call it a "frontend")
needed to make a request of setuptools to take a certain action, for
example, generating a list of installation requirements, the frontend would
would call "setup.py egg_info" or "setup.py bdist_wheel" on the command line.
PEP 517 defines a different method of interfacing with setuptools. Rather
than calling "setup.py" directly, the frontend should:
1. Set the current directory to the directory with a setup.py file
2. Import this module into a safe python interpreter (one in which
setuptools can potentially set global variables or crash hard).
3. Call one of the functions defined in PEP 517.
What each function does is defined in PEP 517. However, here is a "casual"
definition of the functions (this definition should not be relied on for
bug reports or API stability):
- `build_wheel`: build a wheel in the folder and return the basename
- `get_requires_for_build_wheel`: get the `setup_requires` to build
- `prepare_metadata_for_build_wheel`: get the `install_requires`
- `build_sdist`: build an sdist in the folder and return the basename
- `get_requires_for_build_sdist`: get the `setup_requires` to build
Again, this is not a formal definition! Just a "taste" of the module.
N)TemporaryDirectory)parse_requirements)makedirsget_requires_for_build_sdistget_requires_for_build_wheel prepare_metadata_for_build_wheelbuild_wheelbuild_sdist
__legacy__SetupRequirementsErrorc @ s e Zd Zdd ZdS )r c C s
|| _ d S N)
specifiers)selfr
r 9/usr/lib/python3.8/site-packages/setuptools/build_meta.py__init__4 s zSetupRequirementsError.__init__N)__name__
__module____qualname__r r r r r r 3 s c @ s&