Build Tools
Collection of convenience build tools
Autocomplete
build-tools supports autocomplete using argcomplete:
- Install
argcompletethrough your package manager of choice. For example,
uv tool install argcomplete
- Enable autocomplete by adding one of the following to your shell startup file (
~/.zshrc,~/.bashrc, etc):
-
for just
build-tools:eval "$(register-python-argcomplete build-tools)"
-
or globally:
activate-global-python-argcomplete
1 maintainer
Metadata
1 maintainer
Release files for inseven-build-tools 1.1.1
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 | |
|---|---|---|---|---|
| inseven_build_tools-1.1.1.tar.gz | 9.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inseven_build_tools-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.6 kB
Release files / inseven_build_tools-1.1.1.tar.gz
| Download URL | inseven_build_tools-1.1.1.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47cf26e345853f55c80a5c557ef3600d58859bcf0fe5fc8561a722616aa3cac9
|
|
BLAKE2b-256 checksum How to use checksums |
df02a03be864e5504819451bdc439c7a6d645056d2e23f6da0739e0022167c33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logRelease files / inseven_build_tools-1.1.1-py3-none-any.whl
| Download URL | inseven_build_tools-1.1.1-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b17c8a75c88d9f0df66c7438ca2f1adbbb64aa5151cbd91933748f92a79c1df0
|
|
BLAKE2b-256 checksum How to use checksums |
ca7092081599b00804e66b2b81c447a4809ec6b8f749daced4c30746b9f60ba0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logSecurity for inseven-build-tools 1.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for inseven_build_tools-1.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logA 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.
