Minimally improved noise for python. Pragmatic, minimal improved logging for python.
To install use pip install git+git://github.com/jmatt/threepio
----
threepio
========
Minimally improved noise for python.
Pragmatic, minimal logging for python.
# Install
```bash
pip install -e git://github.com/jmatt/threepio#egg=threepio
```
# Use
Just initialize and go.
```python
In [1]: import logging
In [2]: import threepio
In [3]: threepio.initialize(log_filename="./c3po.beep.log",
logger_name="super serial project",
app_logging_level=logging.DEBUG,
dep_logging_level=logging.WARN)
Out[3]: <logging.Logger at 0x106bc4ed0>
In [4]: from threepio import logger as c3po
In [5]: c3po.info("Artoo says that the chances of survival are 725 to 1.")
In [6]: c3po.debug("Actually Artoo has been known to make mistakes...")
In [7]: c3po.warn("from time to time... Oh dear...")
#
# In c3po.beep.log
# 2013-05-01 22:29:47,548 super serial project-INFO [<ipython-input-5-b81c1c01169e> 1] Artoo says that the chances of survival are 725 to 1.
# 2013-05-01 22:30:01,372 super serial project-DEBUG [<ipython-input-6-089fe0b5bf92> 1] Actually Artoo has been known to make mistakes...
# 2013-05-01 22:30:11,602 super serial project-WARN [<ipython-input-7-092eb0b3ce76> 1] From time to time... Oh dear...
```
Or create a custom logger and leave the global logger alone.
```python
In [1]: import logging
In [2]: import threepio
In [3]: woot_logger = threepio.initialize(logger_name="woot",
app_logging_level=logging.DEBUG,
dep_logging_level=logging.DEBUG,
global_logger=False)
In [4]: woot_logger.debug("RWRAharhrhr!")
#
# In the default logging file (threepio.log)
# 2013-05-01 22:14:06,215 woot-DEBUG [<ipython-input-6-3066a630384a> 1] RWRAharhrhr!
```
***[Luke, Leia and Han start laughing hysterically; it sounds like screaming]***
**C-3PO**: Listen to them, they're dying R2! Curse my metal body, I wasn't fast enough, it's all my fault! My poor Master.
**Luke**: 3PO, we're all right! We're all right! Ha ha! Hey, open the pressure maintenance hatch on unit number... where are we? 3263827!
----
For more information, please see: https://github.com/jmatt/threepio
Metadata
Release files for threepio 0.2
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 |
|---|---|---|---|---|
| threepio-0.2.tar.gz | 7.9 kB | Without provenance | Details for threepio-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| threepio-0.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for threepio-0.2-py2.py3-none-any.whl |
Total release size: 13.8 kB
Release files / threepio-0.2.tar.gz
| Download URL | threepio-0.2.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbff6573b765c791bc8df8649824ad4248e365eb7f54094cd8ae77f47479dd4d
|
|
BLAKE2b-256 checksum How to use checksums |
9659660b249c725acb894779b85dde1ac881897e11dbfddc8718f3ff185ca113
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / threepio-0.2-py2.py3-none-any.whl
| Download URL | threepio-0.2-py2.py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3b2558fa11893535e8d1c515e385788366e44cb27350f9a3208d11333d0999a3
|
|
BLAKE2b-256 checksum How to use checksums |
c72010599d420d48b1b7aac91b11a2c0efe4593d1d568599c9653a72f42e6b89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for threepio 0.2
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.