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.0a3
Quick start
Use a standard Python logger and update the status as you work:
import logging
import outwrite
logger = logging.getLogger("my_app")
with outwrite.configure_console(logger=logger):
logger.info("Starting")
outwrite.status.update("Processing files")
# Do your work here.
outwrite.status.clear()
logger.info("Done")
Logs appear above the status line. Cleanup happens automatically when the
with block ends.
Multiple processes
Pass the console connection to each worker and configure it there:
import logging
import multiprocessing as mp
import outwrite
logger = logging.getLogger("my_app")
def work(console_connection: outwrite.ConsoleConnection):
outwrite.configure_console(console_connection)
logger.info("Worker started")
outwrite.status.update("Processing files")
# Do your work here.
logger.info("Worker finished")
if __name__ == "__main__":
ctx = mp.get_context("spawn")
with outwrite.configure_console(logger=logger, mp_context=ctx) as console_connection:
process = ctx.Process(target=work, args=(console_connection,))
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 outwrite.status directly.
See the full example for handling Ctrl+C.
Options
console_level=logging.DEBUGincludes debug logs in the console, without changing existing file handlers.show_status=Falsehides the status line without hiding logs.outwrite.status.clear()clears the line so it can be used again.outwrite.status.disable()immediately hides status in the parent and ignores further updates 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 render_status=your_status_renderer, where
your_status_renderer(text, console) returns a Rich renderable. Both options are
parent-only; workers call outwrite.configure_console(console_connection) without customization.
License
MIT.
Metadata
Release files for outwrite 0.1.0a3
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 |
|---|---|---|---|---|
| outwrite-0.1.0a3.tar.gz | 7.4 kB | With provenance | Details for outwrite-0.1.0a3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| outwrite-0.1.0a3-py3-none-any.whl | Python 3 | none | any | Details for outwrite-0.1.0a3-py3-none-any.whl |
Total release size: 14.0 kB
Release files / outwrite-0.1.0a3.tar.gz
| Download URL | outwrite-0.1.0a3.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
600bfedd99a6e6e679f01be0d105c555ecbc184ec2bad2be357ac4eaa4f85db2
|
|
BLAKE2b-256 checksum How to use checksums |
17a03a2db71c1d25dbaf00e62170b3efc8dbdbe3c1ba051cabb07e855454401f
|
| 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 logRelease files / outwrite-0.1.0a3-py3-none-any.whl
| Download URL | outwrite-0.1.0a3-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d0ee970a4fdd2f6acf729779adb60cbaabe0e4127a486c3675c7738b4fb544c
|
|
BLAKE2b-256 checksum How to use checksums |
90b23537ba944a33f9ba96b1ad8b499c45ae991523c36f5c9990cbf5b03ad8fe
|
| 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 logSecurity for outwrite 0.1.0a3
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 outwrite-0.1.0a3.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 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.