multistage-build 0.1.0
A generic PEP-517 build backend which allows additional processing to be applied to the resulting metadata, wheel and/or editable wheel.
Requires Python: >=3.7

# multistage-build

A generic PEP-517 build backend which allows additional processing to be applied
to the resulting metadata, wheel and/or editable wheel.

## Motivating Example

Sometimes it is desirable to run a post-processing step on a built wheel. For
example, we may wish to inject some additional metadata into the wheel. To do
this, we should write a function which accepts the wheel path as its only
argument, for example:

```python
def my_wheel_post_processing_func(wheel_path):
    print(f'The wheel to be processed is at {wheel_path}')
```

This function can then be declared as post-processing step of the PEP-517
`build_wheel` function:

```toml
[build-system]
requires = [
    'multistage-build',
    'setuptools',
]
build-backend = "multistage_build:backend"

[tool.multistage-build]
build-backend = "setuptools.build_meta"
post-build-wheel = [
    {hook-function="my_mod:my_wheel_post_processing_func", hook-path="."},
]

[project]
name = "some-project"
version = "0.1.0"
...
```

We could also publish this functionality to the package repository, and consume
it by declaring it as a build requirement:

```toml
[build-system]
requires = [
    'multistage-build',
    'my_mod',
    'setuptools',
]
build-backend = "multistage_build:backend"

[tool.multistage-build]
build-backend = "setuptools.build_meta"
post-build-wheel = [
    "my_mod:my_wheel_post_processing_func",
]

[project]
name = "some-project"
version = "0.1.0"
...
```


## Plugin based hooks

For tools wishing to expose a standard behaviour, without requiring the user to
declare each of the hooks manually, it is possible to declare potential hooks
as entrypoints.

An example of a project which automatically registers build-time hooks using entry points:

```toml
[project.entry-points.multistage_build]
post-prepare-metadata-for-build-wheel = "my_mod:prepare_metadata_for_build_wheel_fn"
post-build-wheel = "my_mod:build_editable_fn"
post-build-editable = "my_mod:build_wheel_fn"
```

These hooks will get called for any user of the multistage_build backend, even if
the project declaring these entrypoints doesn't itself use multistage-build.
It allows one to build a library of hooks, and to have consumers add them by
adding extra build dependencies (and declaring a multistage-build backend).

As is normal for entry-points, the name of the function is unimportant.
It is possible to declare multiple entry-points per hook.
A nice pattern would be to only run some behaviour if the hook is configured
in the `pyproject.toml` (which is in the CWD when the hook is running); though
this isn't obligatory (esp. when no configuration is needed - in that case,
the existence of the project in the build environment is enough of a signal for
the hook to be run).

## Status of work

The current functionality includes:

 * Hooks for build-sdist (`post-build-sdist``), build-wheel (`post-build-wheel`), and build-editable
   (`post-build-editable`), and prepare-metadata-for-build-wheel
   (`post-prepare-metadata-for-build-wheel`)
 * Ability to have local definitions included, using the same mechanism as
   in-source builds from PEP-517.

There are a few known features not yet implemented:

 * Hooks for sdist
 * Hooks for all other PEP-517 and PEP-660 hooks
 * Ability to override multiple hooks with a signle declaration (e.g. editable and build hooks). Perhaps allow entrypoint definitions so that you get it simply by having the dependency installed?