Metadata-Version: 2.1
Name: quicklogging
Version: 0.3.1
Summary: helper for easy logging when you're used to print
Home-page: UNKNOWN
Author: "Feth AREZKI (majerti)"
Author-email: "feth.arezki@majerti.fr"
License: UNKNOWN
Platform: UNKNOWN
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Operating System :: OS Independent
Classifier: Development Status :: 5 - Production/Stable
Classifier: Topic :: System :: Logging
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Description-Content-Type: text/x-rst
Provides-Extra: test
License-File: LICENSE

My logging helper library
=========================

Quicklogging is intended for 2 purposes:

  * shrink the boilerplate I need before I can log something by a few bits,
  * help code overhauling from quick and dirty ``print``'ing scripts to
    enterprise class software that can log.

What quicklogging does
======================

Quicklogging provides you with handy loggers named after the current module.



This allows for silencing or raising the logging level for a specific part or a
whole hierarchy of (sub-)packages (ie. folders, in Python's slang).

Quicklogging can catch ``print``. This means that the working code can stay
as-is and still get logged

.. code:: python

    import quicklogging

    # Catches prints in the current module
    quicklogging.catch_prints()

    # Catches prints everywhere in the Python process
    quicklogging.catch_prints(catch_all=True)

What quicklogging does NOT
==========================

Quicklogging does not configure the logging formatting or output as this would
not save any line; here is a basic example for general purpose code: `Quick
survival guide with the logging module
<https://quicklogging.readthedocs.io/en/latest/logging_survival.html>_`.

Quicklogging quality
====================

Quicklogging is covered by a test suite and has been working for years for me, but I wouldn't promise there is no bug.

I have tried documenting the code but would welcome proofreading; the API may change after discussion.


