Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Outwrite

Python logs and live status updates, shared across processes.

Built on Rich.

Requires Python 3.11+. Currently in alpha.

Install

python -m pip install outwrite==0.1.0a2

Quick start

Use a standard Python logger and update the status as you work:

import logging
from outwrite import setup_output, status

logger = logging.getLogger("my_app")

with setup_output(logger=logger):
    logger.info("Starting")
    status.update("Processing files")
    # Do your work here.
    status.clear()
    logger.info("Done")

Logs appear above the status line. Cleanup happens automatically when the with block ends.

Multiple processes

Pass the output connection to each worker and call setup_output(output) there:

import logging
import multiprocessing as mp
from outwrite import setup_output, status

logger = logging.getLogger("my_app")

def work(output):
    setup_output(output)
    logger.info("Worker started")
    status.update("Processing files")
    # Do your work here.
    logger.info("Worker finished")

if __name__ == "__main__":
    ctx = mp.get_context("spawn")
    with setup_output(logger=logger, mp_context=ctx) as output:
        process = ctx.Process(target=work, args=(output,))
        process.start()
        process.join()

Join workers before leaving the with block. Use the same named logger in the parent and workers. Threads can use the configured logger and status directly.

See the full example for handling Ctrl+C.

Options

  • level=logging.DEBUG includes debug logs.
  • show_status=False hides the status line without hiding logs.
  • status.clear() clears the line so it can be used again.
  • status.stop() immediately hides status in the parent for the rest of the session.

Output goes to stderr. Outside a terminal, logs still appear but the status line is hidden.

Custom appearance

Pass console_handler=your_rich_handler to use your own RichHandler formatting, console, and log level. Existing handlers still receive logs; a supplied console handler is not added twice or closed by Outwrite.

For custom status styling, pass status_renderer=format_status, where format_status(text, console) returns a Rich renderable. Both options are parent-only; workers still call setup_output(output) without customization.

License

MIT.

Metadata

Release files for outwrite 0.1.0a2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for outwrite 0.1.0a2
File Size Uploaded Provenance Actions
outwrite-0.1.0a2.tar.gz 7.3 kB With provenance Details for outwrite-0.1.0a2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for outwrite 0.1.0a2
File Interpreter ABI Platform Actions
outwrite-0.1.0a2-py3-none-any.whl Python 3 none any Details for outwrite-0.1.0a2-py3-none-any.whl

Total release size: 13.7 kB

Release files / outwrite-0.1.0a2.tar.gz

Download URL outwrite-0.1.0a2.tar.gz
Size 7.3 kB
Tags Source
SHA-256 checksum
How to use checksums
ab19da8523760ea969f1a19b18d250a4a2eda49a1eb06cefd74cc327fc3d1ddd
BLAKE2b-256 checksum
How to use checksums
070160a6180b2b762eec1a9bf67ccda7688713a00786f40e3ce89f0afc60aee0
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 29, 2026.

Transparency log

Release files / outwrite-0.1.0a2-py3-none-any.whl

Download URL outwrite-0.1.0a2-py3-none-any.whl
Size 6.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e94507bf9e51a9a8b7e3b86554fcfb7853a71b98871ab43c489811ddcc2193c5
BLAKE2b-256 checksum
How to use checksums
412edd9be6f60472c926c68c8edae26fd0f38b320323fee839f9ea0ba62fa479
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 29, 2026.

Transparency log

Security for outwrite 0.1.0a2

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.

Select from 2 files

Attestation for outwrite-0.1.0a2.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 29, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page