ppsetuptools => pyproject setuptools
A drop in replacement for python setuptools that uses pyproject.toml files for python 3.6+ projects
Usage
To install run pip install ppsetuptools in your project.
Place your project settings in the [project] table of your pyproject.toml.
Also ensure that ppsetuptools is included in your [build-system] table
in the requires list.
Replace setuptools import in your setup.py with an import of ppsetuptools.
ppsetuptools exposes all functions from setuptools, and in addition will map
your pyproject.toml data to the call to setuptools.setup for you (via
PEP-621 compliant entries).
Example pyproject.toml
[project]
name = 'my_package'
project_name = 'my_package'
version = '1.0.0'
readme = 'README.md'
install_requires = [
'setuptools',
'toml'
]
include_package_data = true
[build-system]
requires = [
'setuptools >= 40.8.0',
'wheel >= 0.35.1',
'toml >= 0.10.1'
]
build-backend = 'setuptools.build_meta'
Example setup.py
from ppsetuptools import setup
setup()
File locations
As of now, the library attempts to find a pyproject.toml file in the same
directory as the python file that called it. So if calling directly from
setup.py, ensure that your pyproject.toml file is in the same directory.
As well any file references (such as the readme) will attempt to be followed
from this location.
E.g., if including a redme = 'README.md' value, ppsetuptools will look for
README.md in the same directory as the file that called it.
Function support
As of now, ppsetuptools does not support calculated values within the
pyproject.toml file. If calculated values are needed, ppsetuptools
will combine the args passed to the setup call with the values in the
pyproject.toml file, so you may call setup like so, and it will still use your
pyproject.toml values in addition to the passed values.
from ppsetuptools import setup, find_packages
setup(
find_packages(exclude=['tests'])
)
Metadata
Release files for ppsetuptools 2.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ppsetuptools-2.0.2.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ppsetuptools-2.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.4 kB
Release files / ppsetuptools-2.0.2.tar.gz
| Download URL | ppsetuptools-2.0.2.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
736bd1447ba8106fefefdef49be7455797fd45723d4b761161326b1c20b6a489
|
|
BLAKE2b-256 checksum How to use checksums |
00dc1c6533be8f58c6c248625bd8e7e5f4c560df0afe39527086b85884fb3267
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.13
|
Release files / ppsetuptools-2.0.2-py3-none-any.whl
| Download URL | ppsetuptools-2.0.2-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3f5c8ce5f75f4ed72f91a223a964491a001cfdef4926fccfca2e19dd34a9d0e
|
|
BLAKE2b-256 checksum How to use checksums |
0f63be3e98be6c5f5ad496ed465882ee4aff2ead601f2023d2cc8c21e5e6a83f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.13
|
Security for ppsetuptools 2.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.