rn-forge-cli
Documentation · Changelog · Source · All pykit packages
The shared command-line layer for rn-forge-* applications: the Typer
application class, the standard option set and the error-to-exit-code mapping.
Where
rn-forge-commons
is runtime-neutral — safe in a web server, a worker or a container — this
package is the command-line shape. An ordinary batch application wants it just
as much as a developer tool does, which is why it is separate from
rn-forge-tooling,
the package that owns files, installs and rendering. It owns:
app—CliApp, atyper.Typersubclass wiring the standard options into logging and the console;ExitCode; andrun, which applies the mapping to any Typer app. Calling aCliAppreturns an exit code, so[project.scripts]points straight at the app object.options—--log-level,--log-file,--quiet,--json,--dry-run,--yes,--set,CliOptionsandparse_overrides.surface—CliSurface/CommandSurface, the records behind a[cli]table in a config file, from whichCliApp.from_configbuilds the app. Validated on load: a wrong type names the offending key.
Console output is not here — AppConsole lives in rn-forge-commons,
because it is a property of the process rather than of the command-line parser,
and rn_forge.django may not import this package to reach one. This package
drives it: --quiet/--json set its mode.
rn_forge.cli may import rn_forge.commons. It must never import
rn_forge.tooling, and rn_forge.commons must never import either —
.importlinter proves all three.
Installation
Require the package by version range:
dependencies = ["rn-forge-cli>=0.1,<0.2"]
Usage
from rn_forge.cli import CliApp
from rn_forge.commons import console
app = CliApp("golden-app", "Do the thing.")
@app.command()
def greet(name: str) -> None:
"""Greet someone."""
console.success("Hello, {}", name)
[project.scripts]
golden-app = "golden_app.cli:app"
There is no main(): a generated console script is sys.exit(app()), and
CliApp.__call__ returns the mapped exit code.
Or declare the commands in a [cli] table and build the app from it:
app = CliApp.from_config("cli.toml")
Metadata
Release files for rn-forge-cli 0.1.2
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 | Actions |
|---|---|---|---|---|
| rn_forge_cli-0.1.2.tar.gz | 10.0 kB | With provenance | Details for rn_forge_cli-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rn_forge_cli-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for rn_forge_cli-0.1.2-py3-none-any.whl |
Total release size: 21.8 kB
Release files / rn_forge_cli-0.1.2.tar.gz
| Download URL | rn_forge_cli-0.1.2.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36e857f45bdeac19307aefb096809ed2df60bfda983fd14973d6464825f4e830
|
|
BLAKE2b-256 checksum How to use checksums |
1ba69639cee80cde930b26ffe4bcb8c9f4bade77ef625caa376ada59b135419e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","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}
|
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 31, 2026.
Transparency logRelease files / rn_forge_cli-0.1.2-py3-none-any.whl
| Download URL | rn_forge_cli-0.1.2-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
138c7d8edc99b98e1f36a67825cbd52fa417ef3582d8d10371136ad8aa91fc86
|
|
BLAKE2b-256 checksum How to use checksums |
2fd4aa8aac4f4c69e41fd4c99257beb196566208ca23428c508097e3966a6b9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","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}
|
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 31, 2026.
Transparency logSecurity for rn-forge-cli 0.1.2
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
Both files in this release have been uploaded with provenance metadata.
Attestation for rn_forge_cli-0.1.2.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 Oct 31, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.