a

�~�_
�@sXdZd
dl
Z
d
dlZe
jZGdd�de
j�Ze�Zed�
Ze�e�

dd�Z	dd	�Z
dS)
a�Logging utilities for Dulwich.

Any module that uses logging needs to do compile-time initialization to set up
the logging environment. Since Dulwich is also used as a library, clients may
not want to see any logging output. In that case, we need to use a special
handler to suppress spurious warnings like "No handlers could be found for
logger dulwich.foo".

For details on the _NullHandler approach, see:
http://docs.python.org/library/logging.html#configuring-logging-for-a-library

For many modules, the only function from the logging module they need is
getLogger; this module exports that function for convenience. If a calling
module needs something else, it can import the standard logging module
directly.
�Nc@seZ
dZd
Zdd�ZdS)�_NullHandlerz;No-op logging handler to avoid unexpected logging warnings.c
CsdS)
N�)�self�recordrr�3/usr/lib/python3/dist-packages/dulwich/log_utils.py�emit/s
z_NullHandler.emitN)�__name__�
__module__�__qualname__�__doc__rrrrrr,s
rZdulwichcCst�
t
jt
jtjd
d�
dS)z#Set up the default Dulwich loggers.z&%(asctime)s %(levelname)s: %(message)s)�level�stream�formatN)�remove_null_handler�loggingZbasicConfig�INFO�sys�stderrrrrr�default_logging_config8s

�rcCst�
t�

d
S)z�Remove the null handler from the Dulwich loggers.

    If a caller wants to set up logging using something other than
    default_logging_config, calling this function first is a minor optimization
    to avoid the overhead of using the _NullHandler.
    N)�_DULWICH_LOGGERZ
removeHandler�
_NULL_HANDLERrrrrr?sr)rrrZ	getLoggerZHandlerrrrZ
addHandlerrrrrrr�<module>s