Bug#1143885: ITP: pipcl -- Python packaging operations including PEP-517 support
Daniel Echeverri <[email protected]> Fri, 7 Aug 2026 19:32:18 -0500
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <CAJi_FcjCsjT957Laz9N3HKWuTQAkFnQ0_WRgmXrGzZn9mdE5CA__677.459412121095$1786149328$gmane$org@mail.gmail.com> |
Package: wnpp Owner: Daniel Echeverri <[email protected]> Severity: wishlist * Package name : pipcl * Version : 12 * Upstream Author : Julian Smith <[email protected]> * URL or Web page : https://github.com/ArtifexSoftware/pipcl * License : AGPL-3 * Description : Python packaging operations including PEP-517 support * Programming Lang: Python The pipcl package provides Python build backend operations (including PEP 517 support), for use by a setup.py script. - Designed to help build complex Python extension packages. - Can also be used to build simple pure-python packages. - Works on Linux, Windows, MacOS and OpenBSD. - Is a python module, not a framework, so does not impose any restrictions on usage. - Can be used with any external build system by running commands, for example with subprocess.run() or enhanced wrapper pipcl.run(). The intention is to allow a setup.py script to use the full power of Python to do everything that is specific to the package, without having to worry about generic Python packaging issues such wheel formats etc -- Daniel Echeverri Debian Developer Linux user: #477840 GPG Fingerprint: D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB 9F16 8C34 7A2F 57BA BFCC 18DD 3F7B DC71 2C61 410B