LOGKISS (Keep It Simple and Stupid Logger) is a user-friendly logging library for Python. Built on top of the standard logging module, it provides an interface with sensible defaults out of the box.
Features
- Colorful by Default: LOGKISS uses
KissConsoleHandlerby default, which outputs logs in different colors based on log levels. - Drop-in Replacement: Use it as a drop-in replacement for the standard
loggingmodule withimport logkiss as logging. - Flexible Switching: Easily switch back to the standard
ConsoleHandlerwhen needed.
Installation
pip install logkiss
Usage
Minimal Example (Standard logging & logkiss compatibility)
# examples/minimal_warning.py
import logging
logging.warning("Minimal example for beginners")
The same code works with logkiss:
# examples/minimal_warning.py
import logkiss as logging
logging.warning("Minimal example for beginners")
LOGKISS provides three different ways to enhance your logging experience:
1. Colorful Console Logging
Use LOGKISS directly to get beautiful colored log output with minimal setup:
# examples/quickstart_1.py
import logkiss
logger = logkiss.getLogger("example1")
logger.debug("Debug message")
logger.info("Info message")
logger.warning("Warning message")
logger.error("Error message")
logger.critical("Critical error message")
2. Using as a logging module replacement:
# examples/quickstart_2.py
import logkiss as logging
logger2 = logging.getLogger("example2")
logger2.debug("Debug message")
logger2.info("Info message")
logger2.warning("Warning message")
logger2.error("Error message")
logger2.critical("Critical error message")
3. Using custom handler configuration:
# examples/quickstart_3.py
import logging
import logkiss
Get a logger with standard logging module
# examples/quickstart_3.py
logger3 = logging.getLogger("example3")
logger3.setLevel(logging.DEBUG)
logger3.debug("Debug message")
logger3.info("Info message")
logger3.warning("Warning message")
logger3.error("Error message")
logger3.critical("Critical error message")
Clear existing handlers
logger3.handlers.clear()
Add logkiss custom handler
handler = logkiss.KissConsoleHandler() # カラフルな出力用のハンドラー
handler.setFormatter(logkiss.ColoredFormatter(use_color=True))
logger3.addHandler(handler)
Log with customized handler
logger3.error("Customized colorful output")
Sample Output
When you run the above code, you will see output similar to the following:
# Output from logger1.info():
2025-04-08 12:27:43,215 INFO | example.py:5 | Colorful output
# Output from logger2.warning():
2025-04-08 12:27:43,219 WARN | example.py:11 | Also colorful output
# Output from logger3.error():
2025-04-08 12:27:43,224,123 ERROR | example.py:21 | Standard monochrome output
The first two log messages will be displayed with color formatting in your terminal, while the third message will use the standard logging format without colors.
Environment Variables
LOGKISS can be configured using the following environment variables:
LOGKISS_DEBUG: Enable debug mode by setting to1,true, oryes. When enabled:- Root logger's level is set to
DEBUGinstead ofINFO - More detailed logging information is displayed
- Root logger's level is set to
LOGKISS_DISABLE_COLOR: Disable colored output by setting to1,true, oryesNO_COLOR: Disable colored output (the mere presence of this variable, regardless of its value, disables colors) - DEPRECATED: UseLOGKISS_DISABLE_COLORinstead
Example:
# Enable debug mode
export LOGKISS_DEBUG=1
# Run your Python script
python your_script.py
Behavior with Modules and Libraries
Logkiss modifies the behavior of the Python logging system. This has some implications you should be aware of:
Module Interactions
- When you import logkiss in a module, it affects the global logging configuration for the entire Python process
- If you import logkiss in module A, and then import standard logging in module B, the logging in module B will also use logkiss's colorful output
- To switch a specific logger back to standard behavior, use
logkiss.use_console_handler(logger)
Third-Party Library Compatibility
- Most Python libraries that use the standard logging module will automatically benefit from logkiss's colorful output
- However, libraries that define custom handlers or formatters (like matplotlib) may not display colored output
- Libraries that redirect their logs or use advanced logging configurations might have varying results
Best Practices
- In simple applications, importing logkiss at the entry point will colorize logs throughout the application
- For more complex applications, you may want to be more selective about which loggers use colorful output
Configuration
LOGKISS supports multiple configuration methods. You can combine methods compatible with the standard logging library and LOGKISS's own convenient features.
Automatic Configuration
Just importing LOGKISS automatically applies the configuration.
import logkiss
# Configuration is automatically loaded from environment variables and config files
The configuration priority is as follows:
- If the environment variable
LOGKISS_SKIP_CONFIG=1is set, skip loading the configuration file - Configuration file specified by the environment variable
LOGKISS_CONFIG - Configuration file in the default location (e.g.,
~/.config/logkiss/config.yaml) - Configuration from environment variables (
LOGKISS_LEVEL,LOGKISS_FORMAT, etc.)
Main environment variables:
LOGKISS_LEVEL: Specify the log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)LOGKISS_FORMAT: Log format stringLOGKISS_DISABLE_COLOR: Disable coloring (values: 1, true, yes)NO_COLOR: Disable coloring (regardless of the value, just the existence of the environment variable disables it) - DEPRECATED: UseLOGKISS_DISABLE_COLORinstead
Configuration with dictConfig
You can configure using the standard logging.config.dictConfig compatible method.
import logkiss
from logkiss import dictConfig
config = {
"version": 1,
"formatters": {
"colored": {
"()": "logkiss.ColoredFormatter",
"format": "%(asctime)s %(levelname)s | %(filename)s: %(lineno)d | %(message)s",
"colors": { # LOGKISS's unique color settings
"levels": {
"WARNING": {"fg": "black", "bg": "yellow"}
}
}
}
},
"handlers": {
"console": {
"class": "logkiss.KissConsoleHandler",
"level": "DEBUG",
"formatter": "colored"
}
},
"loggers": {
"": {
"handlers": ["console"],
"level": "DEBUG"
}
}
}
dictConfig(config)
Configuration with YAML Files
You can also load configuration from a YAML file.
import logkiss
from logkiss import yaml_config
yaml_config("path/to/config.yaml")
Example YAML file:
version: 1
formatters:
colored:
(): logkiss.ColoredFormatter
format: "%(asctime)s %(levelname)s | %(filename)s: %(lineno)d | %(message)s"
colors:
levels:
WARNING:
fg: black
bg: yellow
handlers:
console:
class: logkiss.KissConsoleHandler
level: DEBUG
formatter: colored
loggers:
"":
handlers: [console]
level: DEBUG
Customizing Color Settings
In LOGKISS, you can customize the colors for each log level. Configure them in dictConfig or YAML file as follows:
"colors": {
"levels": {
"DEBUG": {"fg": "blue"},
"INFO": {"fg": "white"},
"WARNING": {"fg": "black", "bg": "yellow"}, # Black text on yellow background
"ERROR": {"fg": "black", "bg": "red"},
"CRITICAL": {"fg": "black", "bg": "bright_red", "style": "bold"}
},
"elements": {
"timestamp": {"fg": "white"},
"filename": {"fg": "cyan"},
"message": {
"DEBUG": {"fg": "blue"},
"INFO": {"fg": "white"},
"WARNING": {"fg": "black", "bg": "yellow"},
"ERROR": {"fg": "black", "bg": "red"},
"CRITICAL": {"fg": "black", "bg": "bright_red", "style": "bold"}
}
}
}
Available colors and styles:
- Foreground colors (
fg):black,red,green,yellow,blue,magenta,cyan,white,bright_black,bright_red,bright_green,bright_yellow,bright_blue,bright_magenta,bright_cyan,bright_white - Background colors (
bg):black,red,green,yellow,blue,magenta,cyan,white,bright_black,bright_red,bright_green,bright_yellow,bright_blue,bright_magenta,bright_cyan,bright_white - Styles (
style):bold,dim,italic,underline,reverse,hidden,strike
For detailed configuration options, please refer to CONFIG.md.
Acknowledgments
The output format of logkiss is inspired by deigan / loguru
License
This project is licensed under the MIT License - see the LICENSE file for details.
Other Languages
Metadata
Release files for logkiss 2.3.3
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 | |
|---|---|---|---|---|
| logkiss-2.3.3.tar.gz | 29.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| logkiss-2.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.8 kB
Release files / logkiss-2.3.3.tar.gz
| Download URL | logkiss-2.3.3.tar.gz |
|---|---|
| Size | 29.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1928cf1e8e3aa3b44473a4c5e44aba1e360d41d7b99327516fb912a52899344
|
|
BLAKE2b-256 checksum How to use checksums |
9f629c2907936840896d889301f36ffbb5223f60f7bdb9f6448d7490a4208706
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / logkiss-2.3.3-py3-none-any.whl
| Download URL | logkiss-2.3.3-py3-none-any.whl |
|---|---|
| Size | 31.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68ba262c6422837b3268f6ebc65f1fbdb65ed820bc7e43cbcaf97d792cd7193c
|
|
BLAKE2b-256 checksum How to use checksums |
e61869daabf219998d27f728df88204978ad1b0e1f2d204c21ed08addf2c84ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for logkiss 2.3.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.