Skip to main content

Liplog

A simple Python logging package that writes a log file next to your script while also printing messages to the console.

Language

Features

  • Log folder and timestamped log file are created automatically on the first log entry
  • Colored console output in real time
  • Custom levels RUN and SUCCESS
  • No changes to the root logger, so your own logging setup stays untouched

Requirements

  • Python 3.9 or newer

Installation

Install from PyPI:

python -m pip install liplog

Install directly from GitHub:

python -m pip install git+https://github.com/R0g3rT/liplog.git

Update:

python -m pip install --upgrade liplog

Uninstall:

python -m pip uninstall liplog

Usage

from liplog import write_log

write_log("Script started", "RUN")
write_log("Ticket loaded")  # default level: INFO
write_log("Important warning", "WARNING")
write_log("An error occurred", "ERROR")
write_log("Done", "SUCCESS")

Sample output:

[2026-09-14 12:00:00] [RUN] Script started
[2026-09-14 12:00:00] [INFO] Ticket loaded
[2026-09-14 12:00:01] [WARNING] Important warning
[2026-09-14 12:00:02] [ERROR] An error occurred
[2026-09-14 12:00:03] [SUCCESS] Done

Custom log file name (optional, call before the first write_log):

from liplog import setup_logging, write_log

log_file = setup_logging("monthly-report")
write_log(f"Logging to {log_file}")

Supported Log Levels

Level Console color
DEBUG default
RUN blue
INFO default
SUCCESS green
WARNING yellow
ERROR red
CRITICAL magenta

Levels are case-insensitive. An unknown level (e.g. a typo) raises a ValueError.

Note

The log file is saved in logs/<script>/ next to the script that was executed, named <script>-YYYY-MM-DD_HH-MM.log. With setup_logging("name") only the file name changes: logs/<script>/name-YYYY-MM-DD_HH-MM.log.

mailbot.py
logs/
└── mailbot/
    ├── mailbot-2026-11-04_08-30.log
    └── monthly-report-2026-11-04_08-31.log

Console output goes to stdout.

Changes in 0.3.0

  • Log files are stored per script in logs/<script>/ (previously directly in logs/)
  • DEBUG messages are logged
  • Console output goes to stdout (previously stderr)

Changes in 0.2.0

  • Nothing is created on import; folder and file are created on the first log entry
  • RUN and SUCCESS are real log levels (15 and 25)
  • Unknown levels raise ValueError instead of being logged as INFO
  • setup_logging is exported; retries and delay_ms were removed from write_log
  • Requires Python 3.9 or newer

Metadata

Release files for liplog 0.3.0

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

Source distribution (sdist)

Source distribution for liplog 0.3.0
File Size Uploaded Provenance Actions
liplog-0.3.0.tar.gz 4.8 kB With provenance Details for liplog-0.3.0.tar.gz

Built distribution (wheel)

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

Total release size: 9.6 kB

Release files / liplog-0.3.0.tar.gz

Download URL liplog-0.3.0.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
e81721270f05792cfc82ac9c5ba78f3718806ccf04dbb9ba16f75bbcf2d4166a
BLAKE2b-256 checksum
How to use checksums
a8bb54e12726d8a40bc3df3def2259378279485bdc0c51cbffa6d0f62b51311b
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 Nov 4, 2026.

Transparency log

Release files / liplog-0.3.0-py3-none-any.whl

Download URL liplog-0.3.0-py3-none-any.whl
Size 4.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d584ddcef104aa3a26659246eb2b1f38ca60a4c822a4296da6c6bd72dcae6b51
BLAKE2b-256 checksum
How to use checksums
66bae1e77f38df9da50dddd52c4f8adc9535458404bc84296330f8b1c1675ad3
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 Nov 4, 2026.

Transparency log

Security for liplog 0.3.0

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 liplog-0.3.0.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 Nov 4, 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