509318396 ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ 3 yb#@s|dZddlZddlZddlZddlZddlZddlZddlZdadddZ ddd Z d d Z dd d Z Gdddej ZdS)alogging facilities The way to use this is as follows: * each module declares its own logger, using: from .logger import create_logger logger = create_logger() * then each module uses logger.info/warning/debug/etc according to the level it believes is appropriate: logger.debug('debugging info for developers or power users') logger.info('normal, informational output') logger.warning('warn about a non-fatal error or sth else') logger.error('a fatal error') ... and so on. see the `logging documentation `_ for more information * console interaction happens on stderr, that includes interactive reporting functions like `help`, `info` and `list` * ...except ``input()`` is special, because we can't control the stream it is using, unfortunately. we assume that it won't clutter stdout, because interaction would be broken then anyways * what is output on INFO level is additionally controlled by commandline flags NFcCs(dj|||j|}tt}|j|dS)Nz{0}:{1}: {2}: {3})format__name__ create_loggerwarning)messagecategoryfilenamelinenofilelinemsgloggerr/usr/lib64/python3.6/logger.py _log_warning/srBORG_LOGGING_CONFinfocCsd}|rtjj||}|rydtjj|}t|}tjj|WdQRXda tj t }tj d} || _ |j dj|tt_dStk r} zt| }WYdd} ~ XnXtj d}tj|} |r| rd} nd} |rt| ntj| } | j| tj d} | | _|| _ t r.|jr.|jdj|jj|j| |j|jda tj t }|rl|jd j|||j d tt_| S) asetup logging module according to the arguments provided if conf_fname is given (or the config file name can be determined via the env_var, if given): load this logging configuration. otherwise, set up a stream handler logger on stderr (by default, if no stream is provided). if is_serve == True, we configure a special log format as expected by the borg client log message interceptor. NTZborgz+using logging configuration read from "{0}"z/$LOG %(levelname)s %(name)s Remote: %(message)sz %(message)srz*setup_logging for "{0}" failed with "{1}".z,using builtin fallback logging configuration) osenvirongetpathabspathopenloggingconfigZ fileConfig configured getLoggerrjsondebugrrwarnings showwarning ExceptionstrZ StreamHandler JsonFormatter FormatterZ setFormatter formatterZhandlerscloseclearZ addHandlersetLevelupperr)streamZ conf_fnameZenv_varlevelZis_serverZerr_msgfr Z borg_loggererrZhandlerZfmtr&rrr setup_logging8sN              r/c Cs\yBtjj}tj|}x&|dks*|jtkr<|j}tj|}qW|jStk rVtSXdS)zfind the name of the first module calling this module if we cannot find it, we return the current module's name (__name__) instead. N)inspectZ currentframef_backZ getmodulerAttributeError)framemodulerrrfind_parent_modulews  r5csGfddd|S)alazily create a Logger object with the proper path, which is returned by find_parent_module() by default, or is provided via the commandline this is really a shortcut for: logger = logging.getLogger(__name__) we use it to avoid errors and provide a more standard API. We must create the logger lazily, because this is usually called from module level (and thus executed at import time - BEFORE setup_logging() was called). By doing it lazily we can do the setup first, we just have to be careful not to call any logger methods before the setup_logging() call. If you try, you'll get an exception. csneZdZdddZeddZfddZdd Zd d Zd d Z ddZ ddZ ddZ ddZ ddZdS)z!create_logger..LazyLoggerNcSs|pt|_d|_dS)N)r5_LazyLogger__name_LazyLogger__real_logger)selfnamerrr__init__s z*create_logger..LazyLogger.__init__cSsP|jdkrJtstdtj|j|_|jjdrJ|jjtjkrJ|jj d|jS)Nz8tried to call a logger before setup_logging() was calledz borg.debug.ZWARNING) r7rr"rrr6 startswithr,ZNOTSETr))r8rrrZ__loggers  z*create_logger..LazyLogger.__loggercs|jd|S)N.)r6)r8suffix) LazyLoggerrrgetChildsz*create_logger..LazyLogger.getChildc_s|jj||S)N)_LazyLogger__loggerr))r8argskwrrrr)sz*create_logger..LazyLogger.setLevelc_s,d|kr|jd|jdid<|jj||S)Nmsgidextra)pop setdefaultr@log)r8rArBrrrrGsz%create_logger..LazyLogger.logc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@ exception)r8rArBrrrrHsz+create_logger..LazyLogger.exceptionc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@r)r8rArBrrrrsz'create_logger..LazyLogger.debugc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@r)r8rArBrrrrsz&create_logger..LazyLogger.infoc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@r)r8rArBrrrrsz)create_logger..LazyLogger.warningc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@error)r8rArBrrrrIsz'create_logger..LazyLogger.errorc_s,d|kr|jd|jdid<|jj||S)NrCrD)rErFr@critical)r8rArBrrrrJsz*create_logger..LazyLogger.critical)N)r __module__ __qualname__r:propertyr@r?r)rGrHrrrrIrJr)r>rrr>s  r>r)r9r)r>rrs8rcs eZdZdZfddZZS)r$ levelnamer9rrCcsNtj|d|jddd}x&|jD]}t||d}|r$|||<q$Wtj|S)NZ log_messagerZCRITICAL)typeZtimerrN)superrZcreatedRECORD_ATTRIBUTESgetattrrdumps)r8recorddataattrvalue) __class__rrrs    zJsonFormatter.format)rNr9rrC)rrKrLrQr __classcell__rr)rXrr$s  r$)NN)NNrrFF)N)__doc__r0rrZlogging.configZlogging.handlersrr rrr/r5rr%r$rrrrs ? K