Logging functions for log the application info and errors.
Whenever you do:
# pyinstaller, making executable without console
pyinstaller --windowed --onefile your_app.py
Your app not save/display errors, crashes without any info.
This is for that, log the errors to logs folder.
So user send logs to YOU, and you can fix the issues.
Usage:
Don't forget file_path=file to know which file logged the info or module just log itself
from log import *
file = __file__
log("This is an info message.", file_path=file)
log("This is a warning message.", detail="WARNING", file_path=file)
log("This is an error message.", detail="ERROR", file_path=file)
try:
hello
except Exception as e:
log(str(e), detail="error", file_path=file)
# full log info from exception object:
try:
1 / 0
except Exception as e:
loged = get_error_log(e)
log(loged, detail="ERROR", file_path=file)
# or use SimpleLog class for no always file_path parameter:
logger = SimpleLog(file_path=__file__)
logger.info("This is an info message.")
logger.warning("This is a warning message.")
logger.error("This is an error message.")
try:
hello
except Exception as e:
logger.detailed_error(str(e))
Licence:
MIT License
Copyright (c) 2025 Erkhemee
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Additional info (may you have to know it)
FAQ:
- Where is log saved?
The log is in
folder logs, on same location of file that created. Logs sorted by date.
Creators:
Ericwasepic127
Metadata
Release files for log-the-app 1.0.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 |
|---|---|---|---|---|
| log_the_app-1.0.0.tar.gz | 3.7 kB | Without provenance | Details for log_the_app-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| log_the_app-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for log_the_app-1.0.0-py3-none-any.whl |
Total release size: 8.5 kB
Release files / log_the_app-1.0.0.tar.gz
| Download URL | log_the_app-1.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
810e1bfd400225d01e47e831dbe3bcf85124be34181e7973716f55159e68811b
|
|
BLAKE2b-256 checksum How to use checksums |
ea6fe3a0694b8b94b89e73b276cead34f29de75df97bc50a30fbbcc31bd2f6ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / log_the_app-1.0.0-py3-none-any.whl
| Download URL | log_the_app-1.0.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa1ab98c256da0a08ec88e1bdc129709d357152398e9f0bfd9c409be3c68bfde
|
|
BLAKE2b-256 checksum How to use checksums |
8b6aca7e690b67c467f3d7c1834dd409b32bac1b7a9fc8f1bd9a752a17927e99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for log-the-app 1.0.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.