Liplog
A simple Python logging package for creating a log file in the project folder while also printing messages to the console.
Language
Features
- Automatic creation of a log folder
- Timestamped log files
- Console output in real time
- Simple API for quick integration
Installation
Install from PyPI:
python -m pip install liplog
Install directly from GitHub:
git clone https://github.com/R0g3rT/liplog.git
cd liplog
python -m pip install .
Update:
python -m pip install --upgrade liplog
Uninstall:
python -m pip uninstall liplog
Usage
from liplog import write_log
write_log("API client started", "INFO")
write_log("Important warning", "WARNING")
write_log("An error occurred", "ERROR")
Sample output:
[2026-09-14 12:00:00] [INFO] API client started
[2026-09-14 12:00:01] [WARNING] Important warning
[2026-09-14 12:00:02] [ERROR] An error occurred
Supported Log Levels
INFOWARNINGERRORSUCCESSCRITICALRUN
Note
By default, the log file is saved in a logs folder next to the script that was executed.
1 maintainer
Metadata
1 maintainer
Release files for liplog 0.1.7
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 |
|---|---|---|---|---|
| liplog-0.1.7.tar.gz | 3.1 kB | With provenance | Details for liplog-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liplog-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for liplog-0.1.7-py3-none-any.whl |
Total release size: 6.2 kB
Release files / liplog-0.1.7.tar.gz
| Download URL | liplog-0.1.7.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
094fa2cd65f461cc6405ff37dbed57b0af2f79c9b0a41e2d2fb40d8150d8f4b4
|
|
BLAKE2b-256 checksum How to use checksums |
df5234081c8d8adc9544a4f89b21cee4483c130074010f4efd28e9c4734af01b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logRelease files / liplog-0.1.7-py3-none-any.whl
| Download URL | liplog-0.1.7-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
621b26705d883614bf52a667be7ef5f37ca164f4f952d7e0cd2a40cb3af0052c
|
|
BLAKE2b-256 checksum How to use checksums |
c39ba043b039bebb60edd5538a4d524ab99ebb07391ad6eb7d4ab181e1172326
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logSecurity for liplog 0.1.7
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 liplog-0.1.7.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 Sep 17, 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.
