The missing PEP 517 build backend for C extensions.
You know how to build your project. just-buildit knows how to package it. That's the whole deal.
The problem
Every existing Python build backend either wants to own your build system, assumes you're using setuptools extensions, or drags in a dependency tree bigger than your project. There's no option that just says:
"Here are your C files. Build them however you want. I'll ship the result."
just-buildit is that option.
Installation
pip install just-buildit
Quickstart
Flat layouts, nested packages, multiple extensions across subdirectories, mixed pure Python and C — whatever your build produces.
Zero config — a single C extension in src/mylib/:
[build-system]
requires = ["just-buildit"]
build-backend = "just_buildit"
[project]
name = "mylib"
version = "0.1.0"
Run pip install . and just-buildit finds src/mylib/, compiles every .c
file it contains, and ships the result.
Custom build command — Make, CMake, Meson, Bazel, or anything else:
[tool.just-buildit]
command = "make"
just-buildit sets environment variables, calls your command, and packages
everything written to $JUST_BUILDIT_OUTPUT_DIR.
Need a project scaffold? just-makeit generates a CMake-based C extension project pre-wired for just-buildit — see the examples.
CLI
uvx just-buildit inspect # dry-run: show config and what would be built
uvx just-buildit build # build wheel into dist/
uvx just-buildit sdist # build source distribution into dist/
# The version numbers CI cannot read out of a file once the version is
# derived, because there is no longer a file carrying one:
uvx just-buildit --current-version # -> 1.1.4.dev5 (what this tree builds as)
uvx just-buildit --next-version # -> 1.1.4 (what a release would tag)
Documentation
| Environment variables | What just-buildit sets before calling your command |
| Examples | Make, CMake, Meson, Bazel, mixed Python + C, nested packages |
| Configuration | Full config reference, wheel repair, editable installs |
| Contributing | Running tests, platform support, bootstrapping |
Requirements
- Python 3.8+
- A compiler (you already have one)
uvfor wheel repair (uvx auditwheel/uvx delocate-wheel/uvx delvewheel)
Authors
Matthew T. Hunter, Ph.D. and Claude Code
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for just-buildit 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| just_buildit-0.7.0.tar.gz | 217.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| just_buildit-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 256.5 kB
Release files / just_buildit-0.7.0.tar.gz
| Download URL | just_buildit-0.7.0.tar.gz |
|---|---|
| Size | 217.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24524248e273d7be59881e49c2a2f3011ba54a1cb5166c4afd8f3784e106278e
|
|
BLAKE2b-256 checksum How to use checksums |
ccf0a414ded31a943957aed61862198c7080491ada84fc3e933db186b13e7bd5
|
| 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 Oct 4, 2026.
Transparency logRelease files / just_buildit-0.7.0-py3-none-any.whl
| Download URL | just_buildit-0.7.0-py3-none-any.whl |
|---|---|
| Size | 39.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d839f264c8a4f8ee88d66b271ece66c8d7e48cb541731f32954b0d18732c2b5
|
|
BLAKE2b-256 checksum How to use checksums |
4dedd9915a4d461a0f6b44a3b4cb11c4605eccaab3fc8dae35314a1d0107fe57
|
| 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 Oct 4, 2026.
Transparency log
