Friendly misc/utils/convenience library
Overview
runez is a convenience "utils" library for common operations I found myself rewriting multiple times.
The name was initially meant as “run ez” (“run easy”), the fact that it sounds like “runes” gives it a bit of a mystery/magic side that’s also relatively appropriate (it does indeed concentrate a bit of invocation magic, as you can save quite a few lines of repetitive code by using it)
Features
Usable with any python version
Pure python standalone library, does not bring in any additional dependency
Takes care of most edge cases, with nice errors
Functions can be called without checking for return code etc (abort by default, with nice error)
They can also be called with fatal=False, in which case the return value will indicate whether call succeeded or not
Support for dryrun mode (show what would be done, but don’t do it)
Perform most typical logging setups in one call to runez.log.setup()
Log operations systematically (at debug level mostly), examples:
Running: foo ... Copy foo -> bar Would move foo -> bar (for dryrun)
CaptureOutput context manager -> grab output/logging from any code section
100% test coverage
Example
Run a program:
import runez
# Aborts if "foo" doesn't exist
output = runez.run("ls", "foo")
# Output can also be ignored
runez.run("ls", "foo")
# Don't capture output, just run the command and let output "pass through"
runez.run("ls", "foo", stdout=None, stderr=None)
# Don't abort, return False on failure (or actual output when successful)
output = runez.run("ls", "foo", fatal=False)
File operations:
import runez
runez.touch("foo")
runez.copy("foo", "bar")
runez.move("foo", "baz")
runez.delete("foo")
runez.write("foo", "bar\nbaz\n")
content = "\n".join(runez.readlines("foo", first=10))
full_path = runez.resolved_path("foo/bar")
folder = runez.parent_folder(full_path)
runez.ensure_folder(folder)
with runez.Anchored(folder):
assert runez.short(full_path) == "bar"
Installation
As usual, available on pypi: pip install runez
Philosophy
runez tries to provide a consistent interface across functions. Here are the main tenets for functions involving I/O (such as writing, reading, copy-ing files etc):
All IO-related functions NOT returning content (run(), delete(), …) have this common signature: fatal=True, logger=UNSET, dryrun=UNSET
fatal: decides whether operation should raise an exception on failure or not
fatal=True (default): raise an exception on failure, log a meaningful error
fatal=False: don’t raise on failure, log a meaningful error
fatal=None: don’t raise on failure, don’t log anything
In non-fatal mode, calls try to return a usable value appropriate for the call (see docstring of each function)
logger: decides how chatty the operation should be
LOG.error() is used for failures, except when fatal is not True AND provided logger is a callable
logger=UNSET (default):
LOG.debug("Running: ...") to trace activity
print("Would run: ...") in dryrun mode
logger=False: Log errors only (used internally, to avoid unnecessary log chatter when one operation calls another)
logger=mylogger: call provided mylogger() to trace activity (example: logger=MY_LOGGER.info)
mylogger("Running: ...") to trace activity
mylogger("Would run: ...") in dryrun mode
logger=None: Don’t log anything (even errors)
dryrun allows to override current runez.DRYRUN setting just for that call
All IO-related functions returning content (read_json(), readlines(), …) use a simpler convention based on: default=UNSET, which decides whether operation should raise an exception on failure or not:
When default is NOT provided, the function call will abort on failure with an exception, logging a meaningful error via LOG.error()
When default is provided (even if None), the function call will NOT abort, but return the specified default instead, it is up to the caller to log anything in that case (no log chatter comes from runez in that case, at all)
1 maintainer
Metadata
1 maintainer
Release files for runez 5.11.1
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 | |
|---|---|---|---|---|
| runez-5.11.1.tar.gz | 166.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runez-5.11.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 288.4 kB
Release files / runez-5.11.1.tar.gz
| Download URL | runez-5.11.1.tar.gz |
|---|---|
| Size | 166.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7c6baf1959788d832fc8b176da9b9c5fb78924b6529b7b6816c544bb7283871
|
|
BLAKE2b-256 checksum How to use checksums |
45558f17447ba6f575d805a2c1dcf364d4fb781679b5f6c9cc685f3cb78d0d31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 20, 2026.
Transparency logRelease files / runez-5.11.1-py3-none-any.whl
| Download URL | runez-5.11.1-py3-none-any.whl |
|---|---|
| Size | 122.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f54430c28b3ed7be3cbb87dda043e4179dd0215724d3f5f655cfff0ed925061
|
|
BLAKE2b-256 checksum How to use checksums |
09480cd133616a15ea1fd158ac61ebb95fa320a348d1f021d072e9cb90b7c889
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 20, 2026.
Transparency logSecurity for runez 5.11.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for runez-5.11.1.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 20, 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.
