easylogger
easylogger is the most simple way to write your logs . just make a logs object , we can handle session counting and count logs and 6 level of importance for logs (0,5).
logs
the main method just write easylogger.logs("your file dest (default is ./log.txt)","your log name","your log details") for example a=easylogger.logs("./click.log","clicks log","here we have log of clicks from 2012")
logwrite
ogger.logs.logwrite is the only function have three parameters title ,message and degree (0,5) for example a.logwrite("file IO","all of sdcard files are corrupted")
degree
0>>trace 1>>debug 2>>info 3>>warn 4>>err 5>>fatal
Sample Code
import easylogger
a=easylogger.logs("./xapp.log","X app log","all of things happening in X app is written here")
a.logwrite("mouse move","127*148 RU",0)
a.logwrite("hello","127*148 RU",0)
a=None #simulating when app is closed
a=easylogger.logs("./xapp.log","X app log","all of things happening in X app is written here")
a.logwrite("mouse move","127*148 RU",0)
a.logwrite("hello","127*148 RU",0)
Sample Output
xapp.log:
**************** X app log ****************
----------------
all of things happening in X app is written here
----------------
================ Session:0[2018-06-15 04:00:05.612757] ================
[(0,{2018-06-15 04:00:05.612954}) trace >>> mouse move : "127*148 RU"]
[(1,{2018-06-15 04:00:05.613090}) trace >>> hello : "127*148 RU"]
================ Session:1[2018-06-15 04:00:05.613332] ================
[(0,{2018-06-15 04:00:05.613445}) trace >>> mouse move : "127*148 RU"]
[(1,{2018-06-15 04:00:05.613564}) trace >>> hello : "127*148 RU"]
Metadata
Release files for easylogger 2.1.0
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 |
|---|---|---|---|---|
| easylogger-2.1.0.tar.gz | 3.3 kB | Without provenance | Details for easylogger-2.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| easylogger-2.1.0-py3-none-any.whl | Python 3 | none | any | Details for easylogger-2.1.0-py3-none-any.whl |
Total release size: 7.2 kB
Release files / easylogger-2.1.0.tar.gz
| Download URL | easylogger-2.1.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0a39b40a1ee5084f96afecea5afb8575be40e6aa94bdb8cd64c5a1a4ae1e63f
|
|
BLAKE2b-256 checksum How to use checksums |
8c3b56b3ad734a04e7bc1986134174e9dee87991b1bd40d8128afb4037f13583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / easylogger-2.1.0-py3-none-any.whl
| Download URL | easylogger-2.1.0-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
395790b296beafc656ce3a861414249143d4785dfc02671655b9fb5b875474c2
|
|
BLAKE2b-256 checksum How to use checksums |
2c4aef85a40d5e2f99bf2eb05827d1d03689fa3959be892420d7e4afe854bfd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for easylogger 2.1.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.
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.