Skip to main content

pypi actions codecov womm

setuptools-ext

This is a PEP 517 Build backend interface supporting fields in the Core metadata specifications which are otherwise difficult to provide using existing tools. Specifically, it allows declaring those fields marked with an “—” in the rightmost column of the table below by specifying them in a [tool.setuptools-ext] section of pyproject.toml. The backend otherwise functions identically to setuptools.build_meta, and is in fact a drop-in replacement for the default setuptools build backend.

Setuptools lacks a way to specify some fields, despite their validity in Python package metadata according to the spec. PEP 621 – Storing project metadata in pyproject.toml appears to have punted on some of the fields too.

Field

setup.py keyword

pyproject.toml name

Name

name

name

Version

version

version

Dynamic (multiple use)

—

dynamic

Platform (multiple use)

platforms

—

Supported-Platform (multiple use)

—

—

Summary

description

description

Description

long_description

readme

Description-Content-Type

long_description_content_type

readme

Keywords

keywords

keywords

Home-page

url

[project.urls]

Download-URL

download_url

—

Author

author

authors

Author-email

author_email

authors

Maintainer

maintainer

maintainers

Maintainer-email

maintainer_email

maintainers

License

license / license_files

license

Classifier (multiple use)

classifiers

classifiers

Requires-Dist (multiple use)

install_requires

dependencies

Requires-Python

python_requires

requires-python

Requires-External (multiple use)

—

—

Project-URL (multiple-use)

project_urls

[project.urls]

Provides-Extra (multiple use)

extras_require

[project.optional-dependencies]

Provides-Dist (multiple use)

—

—

Obsoletes-Dist (multiple use)

—

—

Reference links for the info above:

Usage

To offer a simple example, if you want to add a Supported-Platform and the Requires-External field three times, producing these lines in the .dist-info/METADATA file:

Supported-Platform: RedHat 8.3
Requires-External: C
Requires-External: libpng (>=1.5)
Requires-External: make; sys_platform != "win32"

You would configure the tool like this in pyproject.toml, specifying a build dependency on setuptools-ext and then adding the fields in a [tool.setuptools-ext] section:

[build-system]
requires = ["setuptools-ext"]
build-backend = "setuptools_ext"

...

[tool.setuptools-ext]
supported-platform = [
    "RedHat 8.3",
]
requires-external = [
    "C",
    "libpng (>=1.5)",
    'make; sys_platform != "win32"'
]

The metadata fields may then be consumed by automated tooling for building RPM packages with system dependencies, for example.

Note: This package does not add new keyword arguments to setup.py (that’s out of scope for a PEP 517 build backend).

Metadata

Release files for setuptools-ext 0.9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for setuptools-ext 0.9
File Size Uploaded Provenance Actions
setuptools_ext-0.9.tar.gz 8.4 kB Without provenance Details for setuptools_ext-0.9.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for setuptools-ext 0.9
File Interpreter ABI Platform Actions
setuptools_ext-0.9-py3-none-any.whl Python 3 none any Details for setuptools_ext-0.9-py3-none-any.whl

Total release size: 15.6 kB

Release files / setuptools_ext-0.9.tar.gz

Download URL setuptools_ext-0.9.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
ced56c030b11ee3991ef7ade25db751c1c5b4e8734c88de648ad2dec572406c6
BLAKE2b-256 checksum
How to use checksums
015875f196d56b8e0949095c209561b2d0b8260a62b797843102b89f6c453464
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.12.2

Release files / setuptools_ext-0.9-py3-none-any.whl

Download URL setuptools_ext-0.9-py3-none-any.whl
Size 7.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8c035cb78e5cdddee5851d77de79ff2ceba68b882795f0a9f385f6a0158d5a3e
BLAKE2b-256 checksum
How to use checksums
58f1195a0e502235efe7716622da766fa3f55d38c7cc89d1bd2796ef2c99713b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.12.2

Security for setuptools-ext 0.9

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page