File: //opt/alt/python37/lib/python3.7/site-packages/loguru/__pycache__/_logger.cpython-37.pyc
B
�P�e�v � @ s� d Z ddlZddlZddlZddlZddlZddlZddlZddlm Z ddl
m Z m Z m
Z
ddlmZmZ ddlmZ ddlmZmZ ddlmZ d d
lmZmZmZm Z d d l m Z d d l m Z d d
l!m"Z" d dl#m$Z$ d dl%m&Z& d dl'm(Z( d dl)m*Z* d dl+m,Z, d dl-m.Z. d dl/m0Z0m1Z1m2Z2m3Z3m4Z4 d dl5m6Z6m7Z7m8Z8m9Z9 ej:dk�rfddl;m<Z< n ddl=m>Z< e dddd d g�Z?e$� Z@e"d i d �ZAG d d!� d!�ZBG d"d#� d#�ZCdS )$a�
.. References and links rendered by Sphinx are kept here as "module documentation" so that they can
be used in the ``Logger`` docstrings but do not pollute ``help(logger)`` output.
.. |Logger| replace:: :class:`~Logger`
.. |add| replace:: :meth:`~Logger.add()`
.. |remove| replace:: :meth:`~Logger.remove()`
.. |complete| replace:: :meth:`~Logger.complete()`
.. |catch| replace:: :meth:`~Logger.catch()`
.. |bind| replace:: :meth:`~Logger.bind()`
.. |contextualize| replace:: :meth:`~Logger.contextualize()`
.. |patch| replace:: :meth:`~Logger.patch()`
.. |opt| replace:: :meth:`~Logger.opt()`
.. |log| replace:: :meth:`~Logger.log()`
.. |level| replace:: :meth:`~Logger.level()`
.. |enable| replace:: :meth:`~Logger.enable()`
.. |disable| replace:: :meth:`~Logger.disable()`
.. |Any| replace:: :obj:`~typing.Any`
.. |str| replace:: :class:`str`
.. |int| replace:: :class:`int`
.. |bool| replace:: :class:`bool`
.. |tuple| replace:: :class:`tuple`
.. |namedtuple| replace:: :func:`namedtuple<collections.namedtuple>`
.. |list| replace:: :class:`list`
.. |dict| replace:: :class:`dict`
.. |str.format| replace:: :meth:`str.format()`
.. |Path| replace:: :class:`pathlib.Path`
.. |match.groupdict| replace:: :meth:`re.Match.groupdict()`
.. |Handler| replace:: :class:`logging.Handler`
.. |sys.stderr| replace:: :data:`sys.stderr`
.. |sys.exc_info| replace:: :func:`sys.exc_info()`
.. |time| replace:: :class:`datetime.time`
.. |datetime| replace:: :class:`datetime.datetime`
.. |timedelta| replace:: :class:`datetime.timedelta`
.. |open| replace:: :func:`open()`
.. |logging| replace:: :mod:`logging`
.. |signal| replace:: :mod:`signal`
.. |contextvars| replace:: :mod:`contextvars`
.. |multiprocessing| replace:: :mod:`multiprocessing`
.. |Thread.run| replace:: :meth:`Thread.run()<threading.Thread.run()>`
.. |Exception| replace:: :class:`Exception`
.. |AbstractEventLoop| replace:: :class:`AbstractEventLoop<asyncio.AbstractEventLoop>`
.. |asyncio.get_running_loop| replace:: :func:`asyncio.get_running_loop()`
.. |asyncio.run| replace:: :func:`asyncio.run()`
.. |loop.run_until_complete| replace::
:meth:`loop.run_until_complete()<asyncio.loop.run_until_complete()>`
.. |loop.create_task| replace:: :meth:`loop.create_task()<asyncio.loop.create_task()>`
.. |logger.trace| replace:: :meth:`logger.trace()<Logger.trace()>`
.. |logger.debug| replace:: :meth:`logger.debug()<Logger.debug()>`
.. |logger.info| replace:: :meth:`logger.info()<Logger.info()>`
.. |logger.success| replace:: :meth:`logger.success()<Logger.success()>`
.. |logger.warning| replace:: :meth:`logger.warning()<Logger.warning()>`
.. |logger.error| replace:: :meth:`logger.error()<Logger.error()>`
.. |logger.critical| replace:: :meth:`logger.critical()<Logger.critical()>`
.. |file-like object| replace:: ``file-like object``
.. _file-like object: https://docs.python.org/3/glossary.html#term-file-object
.. |callable| replace:: ``callable``
.. _callable: https://docs.python.org/3/library/functions.html#callable
.. |coroutine function| replace:: ``coroutine function``
.. _coroutine function: https://docs.python.org/3/glossary.html#term-coroutine-function
.. |re.Pattern| replace:: ``re.Pattern``
.. _re.Pattern: https://docs.python.org/3/library/re.html#re-objects
.. |multiprocessing.Context| replace:: ``multiprocessing.Context``
.. _multiprocessing.Context:
https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods
.. |better_exceptions| replace:: ``better_exceptions``
.. _better_exceptions: https://github.com/Qix-/better-exceptions
.. |loguru-config| replace:: ``loguru-config``
.. _loguru-config: https://github.com/erezinman/loguru-config
.. _Pendulum: https://pendulum.eustace.io/docs/#tokens
.. _@Qix-: https://github.com/Qix-
.. _@erezinman: https://github.com/erezinman
.. _@sdispater: https://github.com/sdispater
.. _formatting directives: https://docs.python.org/3/library/string.html#format-string-syntax
.. _reentrant: https://en.wikipedia.org/wiki/Reentrancy_(computing)
� N)�
namedtuple)�isclass�iscoroutinefunction�isgeneratorfunction)�current_process� get_context)� BaseContext)�basename�splitext)�current_thread� )�
_asyncio_loop� _colorama� _defaults�_filters)�ExceptionFormatter)� Colorizer)�
ContextVar)� aware_now)�ErrorInterceptor)�FileSink)� get_frame)�Handler)�create_logger_lock)�RecordException�
RecordFile� RecordLevel�
RecordProcess� RecordThread)� AsyncSink� CallableSink� StandardSink�
StreamSink)� � )�PathLike)�PurePath�Level�name�no�color�iconZloguru_context)�defaultc @ s$ e Zd Zdd� Zdd� Zdd� ZdS )�Corec C s t dtjtjtj�t dtjtjtj�t dtjtj tj
�t dtj tj tj
�t dtjtjtj�t dtjtjtj�t dtjtjtj�g}dd � |D �| _d
d � | j�� D �d d i�| _d d � | j�� D �| _d
| _i | _ i | _ d | _ t d�| _ i | _!g | _"d| _#t$� | _%d S )N�TRACE�DEBUG�INFO�SUCCESS�WARNING�ERROR�CRITICALc S s i | ] }||j �qS � )r( )�.0�levelr5 r5 �?/opt/alt/python37/lib/python3.7/site-packages/loguru/_logger.py�
<dictcomp>� s z!Core.__init__.<locals>.<dictcomp>c S s i | ]\}}t �|j�|�qS r5 )r �ansifyr* )r6 r( r7 r5 r5 r8 r9 � s � c S s" i | ]\}}|||j |jf|�qS r5 )r) r+ )r6 r( r7 r5 r5 r8 r9 � s r �infT)&r' r ZLOGURU_TRACE_NOZLOGURU_TRACE_COLORZLOGURU_TRACE_ICONZLOGURU_DEBUG_NOZLOGURU_DEBUG_COLORZLOGURU_DEBUG_ICONZLOGURU_INFO_NOZLOGURU_INFO_COLORZLOGURU_INFO_ICONZLOGURU_SUCCESS_NOZLOGURU_SUCCESS_COLORZLOGURU_SUCCESS_ICONZLOGURU_WARNING_NOZLOGURU_WARNING_COLORZLOGURU_WARNING_ICONZLOGURU_ERROR_NOZLOGURU_ERROR_COLORZLOGURU_ERROR_ICONZLOGURU_CRITICAL_NOZLOGURU_CRITICAL_COLORZLOGURU_CRITICAL_ICON�levels�items�levels_ansi_codes�
levels_lookup�handlers_count�handlers�extra�patcher�float� min_level�enabled�activation_list�activation_noner �lock)�selfr= r5 r5 r8 �__init__~ sb
z
Core.__init__c C s | j �� }d |d< |S )NrJ )�__dict__�copy)rK �stater5 r5 r8 � __getstate__� s
zCore.__getstate__c C s | j �|� t� | _d S )N)rM �updater rJ )rK rO r5 r5 r8 � __setstate__� s zCore.__setstate__N)�__name__�
__module__� __qualname__rL rP rR r5 r5 r5 r8 r- } s Gr- c @ st e Zd ZdZdd� Zdd� Zejejej ej
ej ej ej
ejejejd�
dd�ZdHd
d �Zd d
� Zefddd d d dd�dd�Zd dddddddd�dd�Zdd� Zejdd � �Zd d � ZdId d �Z d!d"� Z d#d$� Z d d d d d d%�d&d'�Z d(d)� Z e!i d*d+�d,d-��Z"e!d.d/� �Z#d0d1� Z$d2d3� Z%d4d5� Z&d6d7� Z'd8d9� Z(d:d;� Z)d<d=� Z*d>d?� Z+d@dA� Z,dBdC� Z-dDdE� Z.dFdG� Z/d S )J�Loggera# An object to dispatch logging messages to configured handlers.
The |Logger| is the core object of ``loguru``, every logging configuration and usage pass
through a call to one of its methods. There is only one logger, so there is no need to retrieve
one before usage.
Once the ``logger`` is imported, it can be used to write messages about events happening in your
code. By reading the output logs of your application, you gain a better understanding of the
flow of your program and you more easily track and debug unexpected behaviors.
Handlers to which the logger sends log messages are added using the |add| method. Note that you
can use the |Logger| right after import as it comes pre-configured (logs are emitted to
|sys.stderr| by default). Messages can be logged with different severity levels and they can be
formatted using curly braces (it uses |str.format| under the hood).
When a message is logged, a "record" is associated with it. This record is a dict which contains
information about the logging context: time, function, file, line, thread, level... It also
contains the ``__name__`` of the module, this is why you don't need named loggers.
You should not instantiate a |Logger| by yourself, use ``from loguru import logger`` instead.
c C s" || _ |||||||| |
f | _d S )N)�_core�_options) rK �core� exception�depth�record�lazy�colors�raw�capture�patchersrC r5 r5 r8 rL � s zLogger.__init__c C s dt | jj�� � S )Nz<loguru.logger handlers=%r>)�listrW rB �values)rK r5 r5 r8 �__repr__� s zLogger.__repr__)
r7 �format�filter�colorize� serialize� backtrace�diagnose�enqueue�context�catchc
& K s� | j j� | j j}
| j jd7 _W dQ R X t| |
�}|dkrF|rFd}t|ttf�r�|}d| }|dkrld}t|f| �}i } |j}d}d}�n�t |d��rt
|j ��rt |dd�p�t
|�}|dkr�t�|�}|d kr�t�|�r�t�|�}n|}t|�}t |d
d�}d}d}�n`t|tj��rRt
|�}|dk�r2d}t|�}t |d
d�}d}d}�n t|��sntt |d d���rt |d d��p�t
|�}|dk�r�d}| �d
d�}| �r�|dk�r�y t�� }W n. tk
�r� } ztd�|�W dd}~X Y nX t|��r�|n|j }t |||�}d}d}d}nVt
|��r\t |d d��p6t
|�}|dk�rFd}t |�}d}d}d}nt dt |�j! ��| �r�t dt"t#| �� ��|dk�r�d}�n�|dk�r�t$j%}�n|t|t��r�|d }t&|�}t'j(t$j)||d�}�nJt|t*��r�i } x�|�+� D ]�\} } | dk �r*t| t��s*t dt | �j! ��| dk�r:d} n�| d k�rJd} npt| t��r�y| �,| �j-} W n( tk
�r� td| | f �d�Y nX n(t| t.��r�| } nt d| t | �j!f ��| dk �r�td| | f ��| | | < �q�W t'j(t$j/| d�}n6t
|��r|t0j1k�rtd��|}nt dt |�j! ��t|t��rD| �,|�j-} n$t|t.��rV|} nt d t |�j! ��| dk �r~td | ��t|t��r�yt2�3|| d �}!W n. tk
�r� } ztd �|�W dd}~X Y nX d}"n:t
|��r�|t0j4k�r�td ��|}!d }"nt d!t |�j! ��t|t��s d"}t|
t��r6t5|
�}
n(|
dk �r^t|
t6��s^t d#t |
�j! ��| j j�v t7||||| j8j9j:|d$�}#t||| |!|"|||| |
|
||#| j j;d%�}$| j j<�=� }%|$|%|
< t>| j j?| �| j _?|%| j _<W dQ R X |
S )&uR� Add a handler sending log messages to a sink adequately configured.
Parameters
----------
sink : |file-like object|_, |str|, |Path|, |callable|_, |coroutine function|_ or |Handler|
An object in charge of receiving formatted logging messages and propagating them to an
appropriate endpoint.
level : |int| or |str|, optional
The minimum severity level from which logged messages should be sent to the sink.
format : |str| or |callable|_, optional
The template used to format logged messages before being sent to the sink.
filter : |callable|_, |str| or |dict|, optional
A directive optionally used to decide for each logged message whether it should be sent
to the sink or not.
colorize : |bool|, optional
Whether the color markups contained in the formatted message should be converted to ansi
codes for terminal coloration, or stripped otherwise. If ``None``, the choice is
automatically made based on the sink being a tty or not.
serialize : |bool|, optional
Whether the logged message and its records should be first converted to a JSON string
before being sent to the sink.
backtrace : |bool|, optional
Whether the exception trace formatted should be extended upward, beyond the catching
point, to show the full stacktrace which generated the error.
diagnose : |bool|, optional
Whether the exception trace should display the variables values to eases the debugging.
This should be set to ``False`` in production to avoid leaking sensitive data.
enqueue : |bool|, optional
Whether the messages to be logged should first pass through a multiprocessing-safe queue
before reaching the sink. This is useful while logging to a file through multiple
processes. This also has the advantage of making logging calls non-blocking.
context : |multiprocessing.Context| or |str|, optional
A context object or name that will be used for all tasks involving internally the
|multiprocessing| module, in particular when ``enqueue=True``. If ``None``, the default
context is used.
catch : |bool|, optional
Whether errors occurring while sink handles logs messages should be automatically
caught. If ``True``, an exception message is displayed on |sys.stderr| but the exception
is not propagated to the caller, preventing your app to crash.
**kwargs
Additional parameters that are only valid to configure a coroutine or file sink (see
below).
If and only if the sink is a coroutine function, the following parameter applies:
Parameters
----------
loop : |AbstractEventLoop|, optional
The event loop in which the asynchronous logging task will be scheduled and executed. If
``None``, the loop used is the one returned by |asyncio.get_running_loop| at the time of
the logging call (task is discarded if there is no loop currently running).
If and only if the sink is a file path, the following parameters apply:
Parameters
----------
rotation : |str|, |int|, |time|, |timedelta| or |callable|_, optional
A condition indicating whenever the current logged file should be closed and a new one
started.
retention : |str|, |int|, |timedelta| or |callable|_, optional
A directive filtering old files that should be removed during rotation or end of
program.
compression : |str| or |callable|_, optional
A compression or archive format to which log files should be converted at closure.
delay : |bool|, optional
Whether the file should be created as soon as the sink is configured, or delayed until
first logged message. It defaults to ``False``.
watch : |bool|, optional
Whether or not the file should be watched and re-opened when deleted or changed (based
on its device and inode properties) by an external program. It defaults to ``False``.
mode : |str|, optional
The opening mode as for built-in |open| function. It defaults to ``"a"`` (open the
file in appending mode).
buffering : |int|, optional
The buffering policy as for built-in |open| function. It defaults to ``1`` (line
buffered file).
encoding : |str|, optional
The file encoding as for built-in |open| function. It defaults to ``"utf8"``.
**kwargs
Others parameters are passed to the built-in |open| function.
Returns
-------
:class:`int`
An identifier associated with the added sink and which should be used to
|remove| it.
Raises
------
ValueError
If any of the arguments passed to configure the sink is invalid.
Notes
-----
Extended summary follows.
.. _sink:
.. rubric:: The sink parameter
The ``sink`` handles incoming log messages and proceed to their writing somewhere and
somehow. A sink can take many forms:
- A |file-like object|_ like ``sys.stderr`` or ``open("file.log", "w")``. Anything with
a ``.write()`` method is considered as a file-like object. Custom handlers may also
implement ``flush()`` (called after each logged message), ``stop()`` (called at sink
termination) and ``complete()`` (awaited by the eponymous method).
- A file path as |str| or |Path|. It can be parametrized with some additional parameters,
see below.
- A |callable|_ (such as a simple function) like ``lambda msg: print(msg)``. This
allows for logging procedure entirely defined by user preferences and needs.
- A asynchronous |coroutine function|_ defined with the ``async def`` statement. The
coroutine object returned by such function will be added to the event loop using
|loop.create_task|. The tasks should be awaited before ending the loop by using
|complete|.
- A built-in |Handler| like ``logging.StreamHandler``. In such a case, the `Loguru` records
are automatically converted to the structure expected by the |logging| module.
Note that the logging functions are not `reentrant`_. This means you should avoid using
the ``logger`` inside any of your sinks or from within |signal| handlers. Otherwise, you
may face deadlock if the module's sink was not explicitly disabled.
.. _message:
.. rubric:: The logged message
The logged message passed to all added sinks is nothing more than a string of the
formatted log, to which a special attribute is associated: the ``.record`` which is a dict
containing all contextual information possibly needed (see below).
Logged messages are formatted according to the ``format`` of the added sink. This format
is usually a string containing braces fields to display attributes from the record dict.
If fine-grained control is needed, the ``format`` can also be a function which takes the
record as parameter and return the format template string. However, note that in such a
case, you should take care of appending the line ending and exception field to the returned
format, while ``"\n{exception}"`` is automatically appended for convenience if ``format`` is
a string.
The ``filter`` attribute can be used to control which messages are effectively passed to the
sink and which one are ignored. A function can be used, accepting the record as an
argument, and returning ``True`` if the message should be logged, ``False`` otherwise. If
a string is used, only the records with the same ``name`` and its children will be allowed.
One can also pass a ``dict`` mapping module names to minimum required level. In such case,
each log record will search for it's closest parent in the ``dict`` and use the associated
level as the filter. The ``dict`` values can be ``int`` severity, ``str`` level name or
``True`` and ``False`` to respectively authorize and discard all module logs
unconditionally. In order to set a default level, the ``""`` module name should be used as
it is the parent of all modules (it does not suppress global ``level`` threshold, though).
Note that while calling a logging method, the keyword arguments (if any) are automatically
added to the ``extra`` dict for convenient contextualization (in addition to being used for
formatting).
.. _levels:
.. rubric:: The severity levels
Each logged message is associated with a severity level. These levels make it possible to
prioritize messages and to choose the verbosity of the logs according to usages. For
example, it allows to display some debugging information to a developer, while hiding it to
the end user running the application.
The ``level`` attribute of every added sink controls the minimum threshold from which log
messages are allowed to be emitted. While using the ``logger``, you are in charge of
configuring the appropriate granularity of your logs. It is possible to add even more custom
levels by using the |level| method.
Here are the standard levels with their default severity value, each one is associated with
a logging method of the same name:
+----------------------+------------------------+------------------------+
| Level name | Severity value | Logger method |
+======================+========================+========================+
| ``TRACE`` | 5 | |logger.trace| |
+----------------------+------------------------+------------------------+
| ``DEBUG`` | 10 | |logger.debug| |
+----------------------+------------------------+------------------------+
| ``INFO`` | 20 | |logger.info| |
+----------------------+------------------------+------------------------+
| ``SUCCESS`` | 25 | |logger.success| |
+----------------------+------------------------+------------------------+
| ``WARNING`` | 30 | |logger.warning| |
+----------------------+------------------------+------------------------+
| ``ERROR`` | 40 | |logger.error| |
+----------------------+------------------------+------------------------+
| ``CRITICAL`` | 50 | |logger.critical| |
+----------------------+------------------------+------------------------+
.. _record:
.. rubric:: The record dict
The record is just a Python dict, accessible from sinks by ``message.record``. It contains
all contextual information of the logging call (time, function, file, line, level, etc.).
Each of the record keys can be used in the handler's ``format`` so the corresponding value
is properly displayed in the logged message (e.g. ``"{level}"`` will return ``"INFO"``).
Some records' values are objects with two or more attributes. These can be formatted with
``"{key.attr}"`` (``"{key}"`` would display one by default).
Note that you can use any `formatting directives`_ available in Python's ``str.format()``
method (e.g. ``"{key: >3}"`` will right-align and pad to a width of 3 characters). This is
particularly useful for time formatting (see below).
+------------+---------------------------------+----------------------------+
| Key | Description | Attributes |
+============+=================================+============================+
| elapsed | The time elapsed since the | See |timedelta| |
| | start of the program | |
+------------+---------------------------------+----------------------------+
| exception | The formatted exception if any, | ``type``, ``value``, |
| | ``None`` otherwise | ``traceback`` |
+------------+---------------------------------+----------------------------+
| extra | The dict of attributes | None |
| | bound by the user (see |bind|) | |
+------------+---------------------------------+----------------------------+
| file | The file where the logging call | ``name`` (default), |
| | was made | ``path`` |
+------------+---------------------------------+----------------------------+
| function | The function from which the | None |
| | logging call was made | |
+------------+---------------------------------+----------------------------+
| level | The severity used to log the | ``name`` (default), |
| | message | ``no``, ``icon`` |
+------------+---------------------------------+----------------------------+
| line | The line number in the source | None |
| | code | |
+------------+---------------------------------+----------------------------+
| message | The logged message (not yet | None |
| | formatted) | |
+------------+---------------------------------+----------------------------+
| module | The module where the logging | None |
| | call was made | |
+------------+---------------------------------+----------------------------+
| name | The ``__name__`` where the | None |
| | logging call was made | |
+------------+---------------------------------+----------------------------+
| process | The process in which the | ``name``, ``id`` (default) |
| | logging call was made | |
+------------+---------------------------------+----------------------------+
| thread | The thread in which the | ``name``, ``id`` (default) |
| | logging call was made | |
+------------+---------------------------------+----------------------------+
| time | The aware local time when the | See |datetime| |
| | logging call was made | |
+------------+---------------------------------+----------------------------+
.. _time:
.. rubric:: The time formatting
To use your favorite time representation, you can set it directly in the time formatter
specifier of your handler format, like for example ``format="{time:HH:mm:ss} {message}"``.
Note that this datetime represents your local time, and it is also made timezone-aware,
so you can display the UTC offset to avoid ambiguities.
The time field can be formatted using more human-friendly tokens. These constitute a subset
of the one used by the `Pendulum`_ library of `@sdispater`_. To escape a token, just add
square brackets around it, for example ``"[YY]"`` would display literally ``"YY"``.
If you prefer to display UTC rather than local time, you can add ``"!UTC"`` at the very end
of the time format, like ``{time:HH:mm:ss!UTC}``. Doing so will convert the ``datetime``
to UTC before formatting.
If no time formatter specifier is used, like for example if ``format="{time} {message}"``,
the default one will use ISO 8601.
+------------------------+---------+----------------------------------------+
| | Token | Output |
+========================+=========+========================================+
| Year | YYYY | 2000, 2001, 2002 ... 2012, 2013 |
| +---------+----------------------------------------+
| | YY | 00, 01, 02 ... 12, 13 |
+------------------------+---------+----------------------------------------+
| Quarter | Q | 1 2 3 4 |
+------------------------+---------+----------------------------------------+
| Month | MMMM | January, February, March ... |
| +---------+----------------------------------------+
| | MMM | Jan, Feb, Mar ... |
| +---------+----------------------------------------+
| | MM | 01, 02, 03 ... 11, 12 |
| +---------+----------------------------------------+
| | M | 1, 2, 3 ... 11, 12 |
+------------------------+---------+----------------------------------------+
| Day of Year | DDDD | 001, 002, 003 ... 364, 365 |
| +---------+----------------------------------------+
| | DDD | 1, 2, 3 ... 364, 365 |
+------------------------+---------+----------------------------------------+
| Day of Month | DD | 01, 02, 03 ... 30, 31 |
| +---------+----------------------------------------+
| | D | 1, 2, 3 ... 30, 31 |
+------------------------+---------+----------------------------------------+
| Day of Week | dddd | Monday, Tuesday, Wednesday ... |
| +---------+----------------------------------------+
| | ddd | Mon, Tue, Wed ... |
| +---------+----------------------------------------+
| | d | 0, 1, 2 ... 6 |
+------------------------+---------+----------------------------------------+
| Days of ISO Week | E | 1, 2, 3 ... 7 |
+------------------------+---------+----------------------------------------+
| Hour | HH | 00, 01, 02 ... 23, 24 |
| +---------+----------------------------------------+
| | H | 0, 1, 2 ... 23, 24 |
| +---------+----------------------------------------+
| | hh | 01, 02, 03 ... 11, 12 |
| +---------+----------------------------------------+
| | h | 1, 2, 3 ... 11, 12 |
+------------------------+---------+----------------------------------------+
| Minute | mm | 00, 01, 02 ... 58, 59 |
| +---------+----------------------------------------+
| | m | 0, 1, 2 ... 58, 59 |
+------------------------+---------+----------------------------------------+
| Second | ss | 00, 01, 02 ... 58, 59 |
| +---------+----------------------------------------+
| | s | 0, 1, 2 ... 58, 59 |
+------------------------+---------+----------------------------------------+
| Fractional Second | S | 0 1 ... 8 9 |
| +---------+----------------------------------------+
| | SS | 00, 01, 02 ... 98, 99 |
| +---------+----------------------------------------+
| | SSS | 000 001 ... 998 999 |
| +---------+----------------------------------------+
| | SSSS... | 000[0..] 001[0..] ... 998[0..] 999[0..]|
| +---------+----------------------------------------+
| | SSSSSS | 000000 000001 ... 999998 999999 |
+------------------------+---------+----------------------------------------+
| AM / PM | A | AM, PM |
+------------------------+---------+----------------------------------------+
| Timezone | Z | -07:00, -06:00 ... +06:00, +07:00 |
| +---------+----------------------------------------+
| | ZZ | -0700, -0600 ... +0600, +0700 |
| +---------+----------------------------------------+
| | zz | EST CST ... MST PST |
+------------------------+---------+----------------------------------------+
| Seconds timestamp | X | 1381685817, 1234567890.123 |
+------------------------+---------+----------------------------------------+
| Microseconds timestamp | x | 1234567890123 |
+------------------------+---------+----------------------------------------+
.. _file:
.. rubric:: The file sinks
If the sink is a |str| or a |Path|, the corresponding file will be opened for writing logs.
The path can also contain a special ``"{time}"`` field that will be formatted with the
current date at file creation. The file is closed at sink stop, i.e. when the application
ends or the handler is removed.
The ``rotation`` check is made before logging each message. If there is already an existing
file with the same name that the file to be created, then the existing file is renamed by
appending the date to its basename to prevent file overwriting. This parameter accepts:
- an |int| which corresponds to the maximum file size in bytes before that the current
logged file is closed and a new one started over.
- a |timedelta| which indicates the frequency of each new rotation.
- a |time| which specifies the hour when the daily rotation should occur.
- a |str| for human-friendly parametrization of one of the previously enumerated types.
Examples: ``"100 MB"``, ``"0.5 GB"``, ``"1 month 2 weeks"``, ``"4 days"``, ``"10h"``,
``"monthly"``, ``"18:00"``, ``"sunday"``, ``"w0"``, ``"monday at 12:00"``, ...
- a |callable|_ which will be invoked before logging. It should accept two arguments: the
logged message and the file object, and it should return ``True`` if the rotation should
happen now, ``False`` otherwise.
The ``retention`` occurs at rotation or at sink stop if rotation is ``None``. Files
resulting from previous sessions or rotations are automatically collected from disk. A file
is selected if it matches the pattern ``"basename(.*).ext(.*)"`` (possible time fields are
beforehand replaced with ``.*``) based on the configured sink. Afterwards, the list is
processed to determine files to be retained. This parameter accepts:
- an |int| which indicates the number of log files to keep, while older files are deleted.
- a |timedelta| which specifies the maximum age of files to keep.
- a |str| for human-friendly parametrization of the maximum age of files to keep.
Examples: ``"1 week, 3 days"``, ``"2 months"``, ...
- a |callable|_ which will be invoked before the retention process. It should accept the
list of log files as argument and process to whatever it wants (moving files, removing
them, etc.).
The ``compression`` happens at rotation or at sink stop if rotation is ``None``. This
parameter accepts:
- a |str| which corresponds to the compressed or archived file extension. This can be one
of: ``"gz"``, ``"bz2"``, ``"xz"``, ``"lzma"``, ``"tar"``, ``"tar.gz"``, ``"tar.bz2"``,
``"tar.xz"``, ``"zip"``.
- a |callable|_ which will be invoked before file termination. It should accept the path of
the log file as argument and process to whatever it wants (custom compression, network
sending, removing it, etc.).
Either way, if you use a custom function designed according to your preferences, you must be
very careful not to use the ``logger`` within your function. Otherwise, there is a risk that
your program hang because of a deadlock.
.. _color:
.. rubric:: The color markups
To add colors to your logs, you just have to enclose your format string with the appropriate
tags (e.g. ``<red>some message</red>``). These tags are automatically removed if the sink
doesn't support ansi codes. For convenience, you can use ``</>`` to close the last opening
tag without repeating its name (e.g. ``<red>another message</>``).
The special tag ``<level>`` (abbreviated with ``<lvl>``) is transformed according to
the configured color of the logged message level.
Tags which are not recognized will raise an exception during parsing, to inform you about
possible misuse. If you wish to display a markup tag literally, you can escape it by
prepending a ``\`` like for example ``\<blue>``. If, for some reason, you need to escape a
string programmatically, note that the regex used internally to parse markup tags is
``r"\\?</?((?:[fb]g\s)?[^<>\s]*)>"``.
Note that when logging a message with ``opt(colors=True)``, color tags present in the
formatting arguments (``args`` and ``kwargs``) are completely ignored. This is important if
you need to log strings containing markups that might interfere with the color tags (in this
case, do not use f-string).
Here are the available tags (note that compatibility may vary depending on terminal):
+------------------------------------+--------------------------------------+
| Color (abbr) | Styles (abbr) |
+====================================+======================================+
| Black (k) | Bold (b) |
+------------------------------------+--------------------------------------+
| Blue (e) | Dim (d) |
+------------------------------------+--------------------------------------+
| Cyan (c) | Normal (n) |
+------------------------------------+--------------------------------------+
| Green (g) | Italic (i) |
+------------------------------------+--------------------------------------+
| Magenta (m) | Underline (u) |
+------------------------------------+--------------------------------------+
| Red (r) | Strike (s) |
+------------------------------------+--------------------------------------+
| White (w) | Reverse (v) |
+------------------------------------+--------------------------------------+
| Yellow (y) | Blink (l) |
+------------------------------------+--------------------------------------+
| | Hide (h) |
+------------------------------------+--------------------------------------+
Usage:
+-----------------+-------------------------------------------------------------------+
| Description | Examples |
| +---------------------------------+---------------------------------+
| | Foreground | Background |
+=================+=================================+=================================+
| Basic colors | ``<red>``, ``<r>`` | ``<GREEN>``, ``<G>`` |
+-----------------+---------------------------------+---------------------------------+
| Light colors | ``<light-blue>``, ``<le>`` | ``<LIGHT-CYAN>``, ``<LC>`` |
+-----------------+---------------------------------+---------------------------------+
| 8-bit colors | ``<fg 86>``, ``<fg 255>`` | ``<bg 42>``, ``<bg 9>`` |
+-----------------+---------------------------------+---------------------------------+
| Hex colors | ``<fg #00005f>``, ``<fg #EE1>`` | ``<bg #AF5FD7>``, ``<bg #fff>`` |
+-----------------+---------------------------------+---------------------------------+
| RGB colors | ``<fg 0,95,0>`` | ``<bg 72,119,65>`` |
+-----------------+---------------------------------+---------------------------------+
| Stylizing | ``<bold>``, ``<b>``, ``<underline>``, ``<u>`` |
+-----------------+-------------------------------------------------------------------+
.. _env:
.. rubric:: The environment variables
The default values of sink parameters can be entirely customized. This is particularly
useful if you don't like the log format of the pre-configured sink.
Each of the |add| default parameter can be modified by setting the ``LOGURU_[PARAM]``
environment variable. For example on Linux: ``export LOGURU_FORMAT="{time} - {message}"``
or ``export LOGURU_DIAGNOSE=NO``.
The default levels' attributes can also be modified by setting the ``LOGURU_[LEVEL]_[ATTR]``
environment variable. For example, on Windows: ``setx LOGURU_DEBUG_COLOR "<blue>"``
or ``setx LOGURU_TRACE_ICON "🚀"``. If you use the ``set`` command, do not include quotes
but escape special symbol as needed, e.g. ``set LOGURU_DEBUG_COLOR=^<blue^>``.
If you want to disable the pre-configured sink, you can set the ``LOGURU_AUTOINIT``
variable to ``False``.
On Linux, you will probably need to edit the ``~/.profile`` file to make this persistent. On
Windows, don't forget to restart your terminal for the change to be taken into account.
Examples
--------
>>> logger.add(sys.stdout, format="{time} - {level} - {message}", filter="sub.module")
>>> logger.add("file_{time}.log", level="TRACE", rotation="100 MB")
>>> def debug_only(record):
... return record["level"].name == "DEBUG"
...
>>> logger.add("debug.log", filter=debug_only) # Other levels are filtered out
>>> def my_sink(message):
... record = message.record
... update_db(message, time=record["time"], level=record["level"])
...
>>> logger.add(my_sink)
>>> level_per_module = {
... "": "DEBUG",
... "third.lib": "WARNING",
... "anotherlib": False
... }
>>> logger.add(lambda m: print(m, end=""), filter=level_per_module, level=0)
>>> async def publish(message):
... await api.post(message)
...
>>> logger.add(publish, serialize=True)
>>> from logging import StreamHandler
>>> logger.add(StreamHandler(sys.stderr), format="{message}")
>>> class RandomStream:
... def __init__(self, seed, threshold):
... self.threshold = threshold
... random.seed(seed)
... def write(self, message):
... if random.random() > self.threshold:
... print(message)
...
>>> stream_object = RandomStream(seed=12345, threshold=0.25)
>>> logger.add(stream_object, level="INFO")
r NFz'%s'�
r; �writer( T�encoding�__call__rS �loopz�An event loop is required to add a coroutine sink with `enqueue=True`, but none has been passed as argument and none is currently running.�utf8z"Cannot log to objects of type '%s'z-add() got an unexpected keyword argument '%s'�.)�parent�lengthzVThe filter dict contains an invalid module, it should be a string (or None), not: '%s'r z\The filter dict contains a module '%s' associated to a level name which does not exist: '%s'z�The filter dict contains a module '%s' associated to an invalid level, it should be an integer, a string or a boolean, not: '%s'zqThe filter dict contains a module '%s' associated to an invalid level, it should be a positive integer, not: '%d')�level_per_modulez�The built-in 'filter()' function cannot be used as a 'filter' parameter, this is most likely a mistake (please double-check the arguments passed to 'logger.add()').zFInvalid filter, it should be a function, a string or a dict, not: '%s'z=Invalid level, it should be an integer or a string, not: '%s'z=Invalid level value, it should be a positive integer, not: %dz {exception}z;Invalid format, color markups could not be parsed correctlyz�The built-in 'format()' function cannot be used as a 'format' parameter, this is most likely a mistake (please double-check the arguments passed to 'logger.add()').z>Invalid format, it should be a string or a function, not: '%s'�asciizNInvalid context, it should be a string or a multiprocessing context, not: '%s')rg rp rj ri Zhidden_frames_filename�prefix)r( �sink�levelno� formatter�is_formatter_dynamic�filter_rg rh rk Zmultiprocessing_contextZid_�error_interceptor�exception_formatterr? )@rW rJ rA r �
isinstance�strr% r rp �hasattr�callablero �getattr�reprr Zshould_colorizeZ should_wrap�wrapr" �loggingr r! r �popr
�get_running_loop� RuntimeError�
ValueErrorrq r r � TypeError�typerS �next�iterr Z filter_none�len� functools�partialZfilter_by_name�dictr> r7 r) �intZfilter_by_level�builtinsrf r Zprepare_formatre r r r rm �__code__� co_filenamer? rB rN �minrF )&rK rz r7 re rf rg rh ri rj rk rl rm �kwargs�
handler_idr �pathr( Z wrapped_sinkrp �
terminatorZexception_prefix�streamrr �e�coroZ filter_funcru rv rw �moduleZlevel_Zlevelno_r{ r| r} r� �handlerrB r5 r5 r8 �add� sd "
z
Logger.addNc C s� |dks$t |t�s$tdt|�j ��| jj�� | jj�� }|dk rX||krXt d| �d�|dkrnt
|� � �}n|g}xL|D ]D}|� |�}dd� |�
� D �}t|td�d�| j_|| j_|�� qzW W dQ R X dS )a� Remove a previously added handler and stop sending logs to its sink.
Parameters
----------
handler_id : |int| or ``None``
The id of the sink to remove, as it was returned by the |add| method. If ``None``, all
handlers are removed. The pre-configured handler is guaranteed to have the index ``0``.
Raises
------
ValueError
If ``handler_id`` is not ``None`` but there is no active handler with such id.
Examples
--------
>>> i = logger.add(sys.stderr, format="{message}")
>>> logger.info("Logging")
Logging
>>> logger.remove(i)
>>> logger.info("No longer logging")
NzbInvalid handler id, it should be an integer as returned by the 'add()' method (or None), not: '%s'z'There is no existing handler with id %dc s s | ] }|j V qd S )N)r{ )r6 �hr5 r5 r8 � <genexpr> s z Logger.remove.<locals>.<genexpr>r< )r, )r� r� r� r� rS rW rJ rB rN r� rb �keysr� rc r� rE rF �stop)rK r� rB Z handler_idsr� Zlevelnosr5 r5 r8 �remove� s"
z
Logger.removec sd g � | j j�: | j j�� }x&|�� D ]}|�� � �|�� � q$W W dQ R X G � fdd�d�}|� S )a� Wait for the end of enqueued messages and asynchronous tasks scheduled by handlers.
This method proceeds in two steps: first it waits for all logging messages added to handlers
with ``enqueue=True`` to be processed, then it returns an object that can be awaited to
finalize all logging tasks added to the event loop by coroutine sinks.
It can be called from non-asynchronous code. This is especially recommended when the
``logger`` is utilized with ``multiprocessing`` to ensure messages put to the internal
queue have been properly transmitted before leaving a child process.
The returned object should be awaited before the end of a coroutine executed by
|asyncio.run| or |loop.run_until_complete| to ensure all asynchronous logging messages are
processed. The function |asyncio.get_running_loop| is called beforehand, only tasks
scheduled in the same loop that the current one will be awaited by the method.
Returns
-------
:term:`awaitable`
An awaitable object which ensures all asynchronous logging calls are completed when
awaited.
Examples
--------
>>> async def sink(message):
... await asyncio.sleep(0.1) # IO processing...
... print(message, end="")
...
>>> async def work():
... logger.info("Start")
... logger.info("End")
... await logger.complete()
...
>>> logger.add(sink)
1
>>> asyncio.run(work())
Start
End
>>> def process():
... logger.info("Message sent from the child")
... logger.complete()
...
>>> logger.add(sys.stderr, enqueue=True)
1
>>> process = multiprocessing.Process(target=process)
>>> process.start()
>>> process.join()
Message sent from the child
Nc s e Zd Z� fdd�ZdS )z+Logger.complete.<locals>.AwaitableCompleterc 3 s x� D ]}|� � E d H qW d S )N)� __await__)rK �task)�tasksr5 r8 r� a s
z5Logger.complete.<locals>.AwaitableCompleter.__await__N)rS rT rU r� r5 )r� r5 r8 �AwaitableCompleter` s r� )rW rJ rB rN rc Zcomplete_queue�extendZtasks_to_complete)rK rB r� r� r5 )r� r8 �complete& s 2
zLogger.completer3 Fz�An error has been caught in function '{record[function]}', process '{record[process].name}' ({record[process].id}), thread '{record[thread].name}' ({record[thread].id}):)r7 �reraise�onerror�excluder, �messagec
sT t ��r&t��rt�t�s&| �� ��S | �G � ��������f dd�d�� � d�S )uL Return a decorator to automatically log possibly caught error in wrapped function.
This is useful to ensure unexpected exceptions are logged, the entire program can be
wrapped by this method. This is also very useful to decorate |Thread.run| methods while
using threads to propagate errors to the main logger thread.
Note that the visibility of variables values (which uses the great |better_exceptions|_
library from `@Qix-`_) depends on the ``diagnose`` option of each configured sink.
The returned object can also be used as a context manager.
Parameters
----------
exception : |Exception|, optional
The type of exception to intercept. If several types should be caught, a tuple of
exceptions can be used too.
level : |str| or |int|, optional
The level name or severity with which the message should be logged.
reraise : |bool|, optional
Whether the exception should be raised again and hence propagated to the caller.
onerror : |callable|_, optional
A function that will be called if an error occurs, once the message has been logged.
It should accept the exception instance as it sole argument.
exclude : |Exception|, optional
A type of exception (or a tuple of types) that will be purposely ignored and hence
propagated to the caller without being logged.
default : |Any|, optional
The value to be returned by the decorated function if an error occurred without being
re-raised.
message : |str|, optional
The message that will be automatically logged if an exception occurs. Note that it will
be formatted with the ``record`` attribute.
Returns
-------
:term:`decorator` / :term:`context manager`
An object that can be used to decorate a function or as a context manager to log
exceptions possibly caught.
Examples
--------
>>> @logger.catch
... def f(x):
... 100 / x
...
>>> def g():
... f(10)
... f(0)
...
>>> g()
ERROR - An error has been caught in function 'g', process 'Main' (367), thread 'ch1' (1398):
Traceback (most recent call last):
File "program.py", line 12, in <module>
g()
└ <function g at 0x7f225fe2bc80>
> File "program.py", line 10, in g
f(0)
└ <function f at 0x7f225fe2b9d8>
File "program.py", line 6, in f
100 / x
└ 0
ZeroDivisionError: division by zero
>>> with logger.catch(message="Because we never know..."):
... main() # No exception, no logs
>>> # Use 'onerror' to prevent the program exit code to be 0 (if 'reraise=False') while
>>> # also avoiding the stacktrace to be duplicated on stderr (if 'reraise=True').
>>> @logger.catch(onerror=lambda _: sys.exit(1))
... def main():
... 1 / 0
c sB e Zd Zdd� Zdd� Z�������fdd�Z� �fdd�Zd S )
z Logger.catch.<locals>.Catcherc S s
|| _ d S )N)�_from_decorator)rK �from_decoratorr5 r5 r8 rL � s z&Logger.catch.<locals>.Catcher.__init__c S s d S )Nr5 )rK r5 r5 r8 � __enter__� s z'Logger.catch.<locals>.Catcher.__enter__c s� |d kr d S t |� �sdS �d k r0t |��r0dS | j}�j^}}}}|rP|d7 }|||f|dg| }���||�di � �d k r��|� � S )NFr Tr5 )�
issubclassr� rX �_log) rK �type_�valueZ
traceback_r� �_r[ �optionsZ
catch_options)rZ r� r7 �loggerr� r� r� r5 r8 �__exit__� s
z&Logger.catch.<locals>.Catcher.__exit__c sr t ��rtd�j ���d�� t��r8� ��fdd�}n*t��rR� ��fdd�}n� ��fdd�}t�|�� |S )Nz`Invalid object decorated with 'catch()', it must be a function, not a class (tried to wrap '%s')Tc � s � � �| |�I d H S Q R X �S )Nr5 )�argsr� )�catcherr, �functionr5 r8 �
catch_wrapper� s z=Logger.catch.<locals>.Catcher.__call__.<locals>.catch_wrapperc ? s � � �| |�E d H S Q R X �S )Nr5 )r� r� )r� r, r� r5 r8 r� � s c s � � �| |�S Q R X �S )Nr5 )r� r� )r� r, r� r5 r8 r� � s )r r� rS r r r� �update_wrapper)rK r� r� )�Catcherr, )r� r� r8 rq � s
z&Logger.catch.<locals>.Catcher.__call__N)rS rT rU rL r� r� rq r5 ) r� r, rZ r� r7 r� r� r� r� r5 r8 r� � s r� F)r� r r� �
BaseExceptionrm )rK rZ r7 r� r� r� r, r� r5 ) r� r, rZ r� r7 r� r� r� r� r8 rm g s U "@z Logger.catchTr )rZ r\ r] r^ r_ r` r[ �ansic
C sD |rd}t jdtdd� | jdd� } t| j|||||||f| �� S )a! Parametrize a logging call to slightly change generated log message.
Note that it's not possible to chain |opt| calls, the last one takes precedence over the
others as it will "reset" the options to their default values.
Parameters
----------
exception : |bool|, |tuple| or |Exception|, optional
If it does not evaluate as ``False``, the passed exception is formatted and added to the
log message. It could be an |Exception| object or a ``(type, value, traceback)`` tuple,
otherwise the exception information is retrieved from |sys.exc_info|.
record : |bool|, optional
If ``True``, the record dict contextualizing the logging call can be used to format the
message by using ``{record[key]}`` in the log message.
lazy : |bool|, optional
If ``True``, the logging call attribute to format the message should be functions which
will be called only if the level is high enough. This can be used to avoid expensive
functions if not necessary.
colors : |bool|, optional
If ``True``, logged message will be colorized according to the markups it possibly
contains.
raw : |bool|, optional
If ``True``, the formatting of each sink will be bypassed and the message will be sent
as is.
capture : |bool|, optional
If ``False``, the ``**kwargs`` of logged message will not automatically populate
the ``extra`` dict (although they are still used for formatting).
depth : |int|, optional
Specify which stacktrace should be used to contextualize the logged message. This is
useful while using the logger from inside a wrapped function to retrieve worthwhile
information.
ansi : |bool|, optional
Deprecated since version 0.4.1: the ``ansi`` parameter will be removed in Loguru 1.0.0,
it is replaced by ``colors`` which is a more appropriate name.
Returns
-------
:class:`~Logger`
A logger wrapping the core logger, but transforming logged message adequately before
sending.
Examples
--------
>>> try:
... 1 / 0
... except ZeroDivisionError:
... logger.opt(exception=True).debug("Exception logged with debug level:")
...
[18:10:02] DEBUG in '<module>' - Exception logged with debug level:
Traceback (most recent call last, catch point marked):
> File "<stdin>", line 2, in <module>
ZeroDivisionError: division by zero
>>> logger.opt(record=True).info("Current line is: {record[line]}")
[18:10:33] INFO in '<module>' - Current line is: 1
>>> logger.opt(lazy=True).debug("If sink <= DEBUG: {x}", x=lambda: math.factorial(2**5))
[18:11:19] DEBUG in '<module>' - If sink <= DEBUG: 263130836933693530167218012160000000
>>> logger.opt(colors=True).warning("We got a <red>BIG</red> problem")
[18:11:30] WARNING in '<module>' - We got a BIG problem
>>> logger.opt(raw=True).debug("No formatting\n")
No formatting
>>> logger.opt(capture=False).info("Displayed but not captured: {value}", value=123)
[18:11:41] Displayed but not captured: 123
>>> def wrapped():
... logger.opt(depth=1).info("Get parent context")
...
>>> def func():
... wrapped()
...
>>> func()
[18:11:54] DEBUG in 'func' - Get parent context
Tz?The 'ansi' parameter is deprecated, please use 'colors' instead� )�
stacklevel���N)�warnings�warn�DeprecationWarningrX rV rW )
rK rZ r\ r] r^ r_ r` r[ r� r� r5 r5 r8 �opt s Yz
Logger.optc K s$ | j �^ }}t| jf|||�f�� S )a6 Bind attributes to the ``extra`` dict of each logged message record.
This is used to add custom context to each logging call.
Parameters
----------
**kwargs
Mapping between keys and values that will be added to the ``extra`` dict.
Returns
-------
:class:`~Logger`
A logger wrapping the core logger, but which sends record with the customized ``extra``
dict.
Examples
--------
>>> logger.add(sys.stderr, format="{extra[ip]} - {message}")
>>> class Server:
... def __init__(self, ip):
... self.ip = ip
... self.logger = logger.bind(ip=ip)
... def call(self, message):
... self.logger.info(message)
...
>>> instance_1 = Server("192.168.0.200")
>>> instance_2 = Server("127.0.0.1")
>>> instance_1.call("First instance")
192.168.0.200 - First instance
>>> instance_2.call("Second instance")
127.0.0.1 - Second instance
)rX rV rW )�
_Logger__selfr� r� rC r5 r5 r8 �bindi s ! z Logger.bindc k sZ | j j� t�� |�}t�|�}W dQ R X z
dV W d| j j� t�|� W dQ R X X dS )a� Bind attributes to the context-local ``extra`` dict while inside the ``with`` block.
Contrary to |bind| there is no ``logger`` returned, the ``extra`` dict is modified in-place
and updated globally. Most importantly, it uses |contextvars| which means that
contextualized values are unique to each threads and asynchronous tasks.
The ``extra`` dict will retrieve its initial state once the context manager is exited.
Parameters
----------
**kwargs
Mapping between keys and values that will be added to the context-local ``extra`` dict.
Returns
-------
:term:`context manager` / :term:`decorator`
A context manager (usable as a decorator too) that will bind the attributes once entered
and restore the initial state of the ``extra`` dict while exited.
Examples
--------
>>> logger.add(sys.stderr, format="{message} | {extra}")
1
>>> def task():
... logger.info("Processing!")
...
>>> with logger.contextualize(task_id=123):
... task()
...
Processing! | {'task_id': 123}
>>> logger.info("Done.")
Done. | {}
N)rW rJ rl �get�set�reset)r� r� Z new_context�tokenr5 r5 r8 �
contextualize� s #
zLogger.contextualizec C s* | j �^ }}}t| jf|||g |f�� S )a� Attach a function to modify the record dict created by each logging call.
The ``patcher`` may be used to update the record on-the-fly before it's propagated to the
handlers. This allows the "extra" dict to be populated with dynamic values and also permits
advanced modifications of the record emitted while logging a message. The function is called
once before sending the log message to the different handlers.
It is recommended to apply modification on the ``record["extra"]`` dict rather than on the
``record`` dict itself, as some values are used internally by `Loguru`, and modify them may
produce unexpected results.
The logger can be patched multiple times. In this case, the functions are called in the
same order as they are added.
Parameters
----------
patcher: |callable|_
The function to which the record dict will be passed as the sole argument. This function
is in charge of updating the record in-place, the function does not need to return any
value, the modified record object will be re-used.
Returns
-------
:class:`~Logger`
A logger wrapping the core logger, but which records are passed through the ``patcher``
function before being sent to the added handlers.
Examples
--------
>>> logger.add(sys.stderr, format="{extra[utc]} {message}")
>>> logger = logger.patch(lambda record: record["extra"].update(utc=datetime.utcnow())
>>> logger.info("That's way, you can log messages with time displayed in UTC")
>>> def wrapper(func):
... @functools.wraps(func)
... def wrapped(*args, **kwargs):
... logger.patch(lambda r: r.update(function=func.__name__)).info("Wrapped!")
... return func(*args, **kwargs)
... return wrapped
>>> def recv_record_from_network(pipe):
... record = pickle.loads(pipe.read())
... level, message = record["level"], record["message"]
... logger.patch(lambda r: r.update(record)).log(level, message)
)rX rV rW )rK rD r� ra rC r5 r5 r8 �patch� s .z Logger.patchc C s� t |t�s tdt|�j ��|| kr:| kr:dkrnn n0y | jj| S tk
rl td| �d�Y nX || jjkr�|dkr�td| ��q�d\}}n(|dk r�td| ��n| � |�\}}}}|dkr�|}|dkr�|}t |t
�s�tdt|�j ��|dk �r td | ��t � |�}t
||||�} | jj�T | | jj|< || jj|< ||||f| jj|< x | jj�� D ]}
|
�|� �qhW W dQ R X | S )
u Add, update or retrieve a logging level.
Logging levels are defined by their ``name`` to which a severity ``no``, an ansi ``color``
tag and an ``icon`` are associated and possibly modified at run-time. To |log| to a custom
level, you should necessarily use its name, the severity number is not linked back to levels
name (this implies that several levels can share the same severity).
To add a new level, its ``name`` and its ``no`` are required. A ``color`` and an ``icon``
can also be specified or will be empty by default.
To update an existing level, pass its ``name`` with the parameters to be changed. It is not
possible to modify the ``no`` of a level once it has been added.
To retrieve level information, the ``name`` solely suffices.
Parameters
----------
name : |str|
The name of the logging level.
no : |int|
The severity of the level to be added or updated.
color : |str|
The color markup of the level to be added or updated.
icon : |str|
The icon of the level to be added or updated.
Returns
-------
``Level``
A |namedtuple| containing information about the level.
Raises
------
ValueError
If there is no level registered with such ``name``.
Examples
--------
>>> level = logger.level("ERROR")
>>> print(level)
Level(name='ERROR', no=40, color='<red><bold>', icon='❌')
>>> logger.add(sys.stderr, format="{level.no} {level.icon} {message}")
1
>>> logger.level("CUSTOM", no=15, color="<blue>", icon="@")
Level(name='CUSTOM', no=15, color='<blue>', icon='@')
>>> logger.log("CUSTOM", "Logging...")
15 @ Logging...
>>> logger.level("WARNING", icon=r"/!\")
Level(name='WARNING', no=30, color='<yellow><bold>', icon='/!\\')
>>> logger.warning("Updated!")
30 /!\ Updated!
z4Invalid level name, it should be a string, not: '%s'NzLevel '%s' does not existzILevel '%s' does not exist, you have to create it by specifying a level no)r; � z;Level '%s' already exists, you can't update its severity noz4Invalid level no, it should be an integer, not: '%s'r z:Invalid level no, it should be a positive integer, not: %d)r� r� r� r� rS rW r= �KeyErrorr� r7 r� r r: r' rJ r? r@ rB rc Z
update_format) rK r( r) r* r+ Z old_colorZold_iconr� r� r7 r� r5 r5 r8 r7 � sF 5
"
z Logger.levelc C s | � |d� dS )a_ Disable logging of messages coming from ``name`` module and its children.
Developers of library using `Loguru` should absolutely disable it to avoid disrupting
users with unrelated logs messages.
Note that in some rare circumstances, it is not possible for `Loguru` to
determine the module's ``__name__`` value. In such situation, ``record["name"]`` will be
equal to ``None``, this is why ``None`` is also a valid argument.
Parameters
----------
name : |str| or ``None``
The name of the parent module to disable.
Examples
--------
>>> logger.info("Allowed message by default")
[22:21:55] Allowed message by default
>>> logger.disable("my_library")
>>> logger.info("While publishing a library, don't forget to disable logging")
FN)�_change_activation)rK r( r5 r5 r8 �disableR s zLogger.disablec C s | � |d� dS )a� Enable logging of messages coming from ``name`` module and its children.
Logging is generally disabled by imported library using `Loguru`, hence this function
allows users to receive these messages anyway.
To enable all logs regardless of the module they are coming from, an empty string ``""`` can
be passed.
Parameters
----------
name : |str| or ``None``
The name of the parent module to re-allow.
Examples
--------
>>> logger.disable("__main__")
>>> logger.info("Disabled, so nothing is logged.")
>>> logger.enable("__main__")
>>> logger.info("Re-enabled, messages are logged.")
[22:46:12] Re-enabled, messages are logged.
TN)r� )rK r( r5 r5 r8 �enablej s z
Logger.enable)rB r= rC rD �
activationc s� |dk r� � � ng }|dk r8x|D ]}� jf |� q$W |dk r\� jj� |� j_W dQ R X |dk r�� jj� � jj�� � jj�|� W dQ R X |dk r�x*|D ]"\}}|r�� �|� q�� � |� q�W � fdd�|D �S )u� Configure the core logger.
It should be noted that ``extra`` values set using this function are available across all
modules, so this is the best way to set overall default values.
To load the configuration directly from a file, such as JSON or YAML, it is also possible to
use the |loguru-config|_ library developed by `@erezinman`_.
Parameters
----------
handlers : |list| of |dict|, optional
A list of each handler to be added. The list should contain dicts of params passed to
the |add| function as keyword arguments. If not ``None``, all previously added
handlers are first removed.
levels : |list| of |dict|, optional
A list of each level to be added or updated. The list should contain dicts of params
passed to the |level| function as keyword arguments. This will never remove previously
created levels.
extra : |dict|, optional
A dict containing additional parameters bound to the core logger, useful to share
common properties if you call |bind| in several of your files modules. If not ``None``,
this will remove previously configured ``extra`` dict.
patcher : |callable|_, optional
A function that will be applied to the record dict of each logged messages across all
modules using the logger. It should modify the dict in-place without returning anything.
The function is executed prior to the one possibly added by the |patch| method. If not
``None``, this will replace previously configured ``patcher`` function.
activation : |list| of |tuple|, optional
A list of ``(name, state)`` tuples which denotes which loggers should be enabled (if
``state`` is ``True``) or disabled (if ``state`` is ``False``). The calls to |enable|
and |disable| are made accordingly to the list order. This will not modify previously
activated loggers, so if you need a fresh start prepend your list with ``("", False)``
or ``("", True)``.
Returns
-------
:class:`list` of :class:`int`
A list containing the identifiers of added sinks (if any).
Examples
--------
>>> logger.configure(
... handlers=[
... dict(sink=sys.stderr, format="[{time}] {message}"),
... dict(sink="file.log", enqueue=True, serialize=True),
... ],
... levels=[dict(name="NEW", no=13, icon="¤", color="")],
... extra={"common_to_all": "default"},
... patcher=lambda record: record["extra"].update(some_value=42),
... activation=[("my_module.secret", False), ("another_library.module", True)],
... )
[1, 2]
>>> # Set a default "extra" dict to logger across all modules, without "bind()"
>>> extra = {"context": "foo"}
>>> logger.configure(extra=extra)
>>> logger.add(sys.stderr, format="{extra[context]} - {message}")
>>> logger.info("Context without bind")
>>> # => "foo - Context without bind"
>>> logger.bind(context="bar").info("Suppress global context")
>>> # => "bar - Suppress global context"
Nc s g | ]}� j f |��qS r5 )r� )r6 �params)rK r5 r8 �
<listcomp>� s z$Logger.configure.<locals>.<listcomp>)
r� r7 rW rJ rD rC �clearrQ r� r� ) rK rB r= rC rD r� r� r( rO r5 )rK r8 � configure� s& ?
zLogger.configurec sD � d ks$t � t�s$tdt� �j ��| jj�� | jj�� }� d krvx |D ]}|d krJ|||< qJW || j_ || j_d S � dkr�� d7 � � fdd�| jj
D �}t � fdd�|D �d �}||kr� dkr�|dks�|� � |f� d d
� }|j
|dd � x4|D ],}|d k r�|d d t� �� � kr�|||< q�W || j_
|| j_W d Q R X d S ) Nz8Invalid name, it should be a string (or None), not: '%s'r; rt c s, g | ]$\}}|d t � �� � kr||f�qS )N)r� )r6 �n�s)r( r5 r8 r� � s z-Logger._change_activation.<locals>.<listcomp>c 3 s* | ]"\}}� d t |�� |kr|V qd S )N)r� )r6 r� r� )r( r5 r8 r� � s z,Logger._change_activation.<locals>.<genexpr>Tc S s | d � d�S )Nr rt )�count)�xr5 r5 r8 �
modules_depth� s z0Logger._change_activation.<locals>.modules_depth)�key�reverse)r� r� r� r� rS rW rJ rG rN rI rH r� �append�sortr� )rK r( �statusrG r� rH Z
parent_statusr� r5 )r( r8 r� � s2
zLogger._change_activationi )�cast�chunkc # s t | ttf�r d}tt| ��}n0t| d�r>t| j�r>d}| }ntdt| �j ��t � t
�rh� fdd�}n t� �rv� }ntdt� �j ��yt � |�}W n( tk
r� tdt|�j �d �Y nX t
�|||�}x"|D ]} | �� }
||
� |
V q�W |r�|�� d S )
a� Parse raw logs and extract each entry as a |dict|.
The logging format has to be specified as the regex ``pattern``, it will then be
used to parse the ``file`` and retrieve each entry based on the named groups present
in the regex.
Parameters
----------
file : |str|, |Path| or |file-like object|_
The path of the log file to be parsed, or an already opened file object.
pattern : |str| or |re.Pattern|_
The regex to use for logs parsing, it should contain named groups which will be included
in the returned dict.
cast : |callable|_ or |dict|, optional
A function that should convert in-place the regex groups parsed (a dict of string
values) to more appropriate types. If a dict is passed, it should be a mapping between
keys of parsed log dict and the function that should be used to convert the associated
value.
chunk : |int|, optional
The number of bytes read while iterating through the logs, this avoids having to load
the whole file in memory.
Yields
------
:class:`dict`
The dict mapping regex named groups to matched values, as returned by |match.groupdict|
and optionally converted according to ``cast`` argument.
Examples
--------
>>> reg = r"(?P<lvl>[0-9]+): (?P<msg>.*)" # If log format is "{level.no} - {message}"
>>> for e in logger.parse("file.log", reg): # A file line could be "10 - A debug message"
... print(e) # => {'lvl': '10', 'msg': 'A debug message'}
>>> caster = dict(lvl=int) # Parse 'lvl' key as an integer
>>> for e in logger.parse("file.log", reg, cast=caster):
... print(e) # => {'lvl': 10, 'msg': 'A debug message'}
>>> def cast(groups):
... if "date" in groups:
... groups["date"] = datetime.strptime(groups["date"], "%Y-%m-%d %H:%M:%S")
...
>>> with open("file.log") as file:
... for log in logger.parse(file, reg, cast=cast):
... print(log["date"], log["something_else"])
T�readFzDInvalid file, it should be a string path or a file object, not: '%s'c s2 x,� � � D ] \}}|| kr
|| | �| |< q
W d S )N)r> )�groupsr� � converter)r� r5 r8 �
cast_functionB s z#Logger.parse.<locals>.cast_functionz:Invalid cast, it should be a function or a dict, not: '%s'zEInvalid pattern, it should be a string or a compiled regex, not: '%s'N)r� r� r% �openr� r� r� r� r� rS r� �re�compilerV �
_find_iter� groupdict�close) �file�patternr� r� Z should_close�fileobjr� �regex�matches�matchr� r5 )r� r8 �parse s: 0
z Logger.parsec c sz | � d�}xj| � |�}||7 }t|�|��}|s<|E d H P t|�dkr |d �� }||d � }|d d� E d H q W d S )Nr r r� ���)r� rb �finditerr� �end)r� r� r� �buffer�textr� r� r5 r5 r8 r� ` s
zLogger._find_iterc * C s� | j }|jsd S y|j| \}} }
} W n� ttfk
r� t|t�rRtd| �d �t|t�sptdt |�j
�d �|dk r�td| �d �d d| |df} | \}} }
} | |j|< Y nX |
|j k r�d S |\ }
}}}}}}}}t |d �}y|j
d }W n tk
�r
d }Y nX y|j| �s d S W n� tk
�r� |j}|d k�r\|j}|||< |�s�d S nP|d }x>|jD ]4\}}|d t|�� |k�rl|�r�P d
||< d S �qlW d ||< Y nX t� } |j} | j} t| �} t� } t� }!| t }"|
�r>t|
t��r
t |
�|
|
j }#}$}%n&t|
t��r"|
\}#}$}%nt � � \}#}$}%t |#|$|%�}
nd }
|"|
|j t �!� |�t"| | �| j#t$| |
| �|j%t|�t&| �d |t'|!j(|!j)�t*| j(| j)�| d �
}&|�r�d
d� |D �}dd� |�+� D �}|�r�|�r�|&d �,|� |�rd|k�r�td��|j,|&d� |�r@|�s|�r&t-�.|||�}'nt-�/t|��}'|'j0|&d< n&|�sL|�rbd }'|j1||�|&d< nd }'|j2�rx|�2|&� x|D ]}(|(|&� �q~W x&|j�3� D ]})|)�4|&||||'� �q�W d S )NzLevel '%s' does not existz=Invalid level, it should be an integer or a string, not: '%s'r z=Invalid level value, it should be a positive integer, not: %dzLevel %dr� r� rS rt FT)
�elapsedrZ rC r� r� r7 �liner� r� r( �process�thread�timec S s g | ]
}|� �qS r5 r5 )r6 �argr5 r5 r8 r� � s z Logger._log.<locals>.<listcomp>c S s i | ]\}}|� |�qS r5 r5 )r6 r� r� r5 r5 r8 r9 � s z Logger._log.<locals>.<dictcomp>rC r\ z�The message can't be formatted: 'record' shall not be used as a keyword argument while logger has been configured with '.opt(record=True)')r\ r� )5rW rB r@ r� r� r� r� r� r� r� rS rF r � f_globalsrG rI rH r� r �f_coder� r r r �
start_timer� �
__traceback__�tuple�sys�exc_infor rC rl r� r �co_namer �f_linenor
r �identr( r r> rQ r Zprepare_messageZprepare_simple_message�strippedre rD rc �emit)*rK r7 r� r� r� r� r� rY Zlevel_id�
level_nameZlevel_noZ
level_icon�cacherZ r[ r\ r] r^ r_ r` ra rC �framer( rG r� Z dotted_nameZdotted_module_nameZcurrent_datetime�code� file_path� file_namer r r r� r� � tracebackZ
log_recordZcolored_messagerD r� r5 r5 r8 r� r s�
z Logger._logc O s | � dd| j|||� dS )zBLog ``message.format(*args, **kwargs)`` with severity ``'TRACE'``.r. FN)r� rX )r� �_Logger__messager� r� r5 r5 r8 �trace� s z Logger.tracec O s | � dd| j|||� dS )zBLog ``message.format(*args, **kwargs)`` with severity ``'DEBUG'``.r/ FN)r� rX )r� r r� r� r5 r5 r8 �debug� s z Logger.debugc O s | � dd| j|||� dS )zALog ``message.format(*args, **kwargs)`` with severity ``'INFO'``.r0 FN)r� rX )r� r r� r� r5 r5 r8 �info� s z Logger.infoc O s | � dd| j|||� dS )zDLog ``message.format(*args, **kwargs)`` with severity ``'SUCCESS'``.r1 FN)r� rX )r� r r� r� r5 r5 r8 �success� s zLogger.successc O s | � dd| j|||� dS )zDLog ``message.format(*args, **kwargs)`` with severity ``'WARNING'``.r2 FN)r� rX )r� r r� r� r5 r5 r8 �warning s zLogger.warningc O s | � dd| j|||� dS )zBLog ``message.format(*args, **kwargs)`` with severity ``'ERROR'``.r3 FN)r� rX )r� r r� r� r5 r5 r8 �error s z Logger.errorc O s | � dd| j|||� dS )zELog ``message.format(*args, **kwargs)`` with severity ``'CRITICAL'``.r4 FN)r� rX )r� r r� r� r5 r5 r8 �critical
s zLogger.criticalc O s* d| j dd� }| �dd||||� dS )zIConvenience method for logging an ``'ERROR'`` with exception information.)Tr Nr3 F)rX r� )r� r r� r� r� r5 r5 r8 rZ s zLogger.exceptionc O s | � |d| j|||� dS )z@Log ``message.format(*args, **kwargs)`` with severity ``level``.FN)r� rX )r� Z_Logger__levelr r� r� r5 r5 r8 �log s z
Logger.logc O s t jdtdd� | j||�S )z�Deprecated function to |add| a new handler.
Warnings
--------
.. deprecated:: 0.2.2
``start()`` will be removed in Loguru 1.0.0, it is replaced by ``add()`` which is a less
confusing name.
z>The 'start()' method is deprecated, please use 'add()' insteadr� )r� )r� r� r� r� )rK r� r� r5 r5 r8 �start s
z Logger.startc O s t jdtdd� | j||�S )z�Deprecated function to |remove| an existing handler.
Warnings
--------
.. deprecated:: 0.2.2
``stop()`` will be removed in Loguru 1.0.0, it is replaced by ``remove()`` which is a less
confusing name.
z@The 'stop()' method is deprecated, please use 'remove()' insteadr� )r� )r� r� r� r� )rK r� r� r5 r5 r8 r� ' s
z Logger.stop)N)NNN)0rS rT rU �__doc__rL rd r Z LOGURU_LEVELZ
LOGURU_FORMATZ
LOGURU_FILTERZLOGURU_COLORIZEZLOGURU_SERIALIZEZLOGURU_BACKTRACEZLOGURU_DIAGNOSEZLOGURU_ENQUEUEZLOGURU_CONTEXTZ LOGURU_CATCHr� r� r� � Exceptionrm r� r� �
contextlib�contextmanagerr� r� r7 r� r� r� r� � staticmethodr� r� r� r r r r r r r! rZ r" r# r� r5 r5 r5 r8 rV � sz
1C Z$-1
gZ([ rV )Dr$ r� r& r� r� r� r r� � collectionsr �inspectr r r �multiprocessingr r Zmultiprocessing.contextr �os.pathr r
� threadingr r; r
r r r Z_better_exceptionsr Z
_colorizerr � _contextvarsr � _datetimer Z_error_interceptorr Z
_file_sinkr Z
_get_framer Z_handlerr Z_locks_machineryr Z _recattrsr r r r r Z
_simple_sinksr r r! r" � version_info�osr% �pathlibr& r' r rl r- rV r5 r5 r5 r8 �<module>T sB R