This release is a pre-release and may not be stable for production use.
bazaar-contrib-invoke
Accept COMMANDS to register Click commands in your contrib's lifespan:
from contextlib import asynccontextmanager
import click
from bazaar_contrib_invoke import COMMANDS, CommandEntry
from bazaar_core import Context, Contrib
@click.command("hello", help="Say hello.")
@click.argument("name")
def hello(name: str) -> None:
click.echo(f"Hello, {name}!")
@asynccontextmanager
async def lifespan(ctx: Context):
with ctx.accept(COMMANDS).register(hello):
yield
example = Contrib(accepts=[COMMANDS], lifespan=lifespan)
hello_entry = CommandEntry(contrib="example", help="Say hello.")
Declare both entry points in your package's pyproject.toml:
[project.entry-points."bazaar_compute_node.contribs"]
example = "example_package:example"
[project.entry-points."bazaar_compute_node.commands"]
hello = "example_package:hello_entry"
Install and enable the package:
bcn contrib add invoke --enable
bcn contrib add example-package --enable example
The corresponding entries in config.toml:
version = "5"
[[contribs]]
package = "bazaar-contrib-invoke~=0.3.0rc1"
[[contribs.enabled]]
entry = "commands"
[[contribs]]
package = "example-package>=0.1.0"
[[contribs.enabled]]
entry = "example"
Then run bcn hello Alice.
Async command callbacks call shared services directly to reuse business logic.
Calling Click Context.invoke() or Context.forward() from an async callback raises
RuntimeError before invoking the target callback.
A command entry that fails to load is reported independently. Other commands remain available; selecting the failed command reports its loading error.
Metadata
Release files for bazaar-contrib-invoke 0.3.0rc1
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 | |
|---|---|---|---|---|
| bazaar_contrib_invoke-0.3.0rc1.tar.gz | 8.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bazaar_contrib_invoke-0.3.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.2 kB
Release files / bazaar_contrib_invoke-0.3.0rc1.tar.gz
| Download URL | bazaar_contrib_invoke-0.3.0rc1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20fad1f64893540cffeb7a19e8ed1e2f27bd44465ceb59a6b02a98236cc7fa39
|
|
BLAKE2b-256 checksum How to use checksums |
7bfab9e41825c9e3e2a358cab5f0829d3d0e6ff78e624b73b9029585a4e09d3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / bazaar_contrib_invoke-0.3.0rc1-py3-none-any.whl
| Download URL | bazaar_contrib_invoke-0.3.0rc1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
931ae3a753e1ae0c78fe62ca411e7999b1badeb7c07d0b6e6d7659812bcf2787
|
|
BLAKE2b-256 checksum How to use checksums |
2f71048239562326ac34f852faa826bc8ecedc111807e02c8ac6cfcb180bc736
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for bazaar-contrib-invoke 0.3.0rc1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.