livery.extensions.nanobind._tasks¶
livery.extensions.nanobind._tasks ¶
The nanobind extension's verb, loaded through the extension's entry point.
Importing this module registers the nanobind group and its hidden
wheels verb, which each leg of the release point's wheels job runs.
The job, the key that names its legs and the publish job's wait on it
are declared in the extension's extension.toml; the labels and the
build each leg runs are the extension's _ci module's. The base's
plugin never imports this module.
Functions:
| Name | Description |
|---|---|
cibw_build_set |
The cibuildwheel build identifiers for pythons, space-separated. |
nanobind_wheels |
Build this runner's native artifacts for the release at HEAD. |
Attributes:
| Name | Type | Description |
|---|---|---|
nanobind |
|
nanobind
module-attribute
¶
nanobind = group('nanobind', help="The platform wheels of nanobind's packages")
cibw_build_set ¶
The cibuildwheel build identifiers for pythons, space-separated.
3.14 becomes cp314-* and a free-threaded 3.14t becomes
cp314t-*, so a wheels leg builds exactly the interpreters the
workspace's python matrix names, on every libc flavour of its
platform, instead of every CPython cibuildwheel knows.
Source code in packages/extensions/nanobind/src/livery/extensions/nanobind/_tasks.py
nanobind_wheels ¶
nanobind_wheels(ctx: Context) -> None
Build this runner's native artifacts for the release at HEAD.
The wheels job's one entry, on each of its legs. The job checks out the release squash the wave publishes, so HEAD is the release. The build is the extension's host build over the workspace's whole python matrix. A release that holds no native package builds nothing and says so, so the leg stays green on a pure release.
Raises:
| Type | Description |
|---|---|
Failed
|
when no workspace contract is above the working directory. |