a Df1@sdZddlZddlZddlZddlmZddlmZmZz ddl Z Wne yZdZ Yn0z ddl Z Wne y~dZ Yn0ddl m Z mZmZmZedZedZedZed d d Zeed d dZGdddejZdeeejddddZdeddddZdS)aHLogging support for Tornado. Tornado uses three logger streams: * ``tornado.access``: Per-request logging for Tornado's HTTP servers (and potentially other servers in the future) * ``tornado.application``: Logging of errors from application code (i.e. uncaught exceptions from callbacks) * ``tornado.general``: General-purpose logging, including any errors or warnings from Tornado itself. These streams may be configured independently using the standard library's `logging` module. For example, you may wish to send ``tornado.access`` logs to a separate file for analysis. N)_unicode) unicode_typebasestring_type)DictAnycastOptionalztornado.accessztornado.applicationztornado.general)returncCstz\ttjdrZtjrZtr:ttddkrZWdSn trZtjttj dt urZWdSWnt ynYn0dS)NisattycolorsrTwrapped_stderrF) hasattrsysstderrr cursesZ setuptermZtigetnumcoloramagetattr initialiseobject ExceptionrrX/nfs/NAS7/SABIOD/METHODE/ermites/ermites_venv/lib/python3.9/site-packages/tornado/log.py_stderr_supports_color7s   r)sr cCs*z t|WSty$t|YS0dSN)rUnicodeDecodeErrorrepr)rrrr _safe_unicodeJs  rc @sveZdZdZdZdZejdejdej dej dej diZ eed d e fe e e eeeefd d d dZee dddZd S) LogFormatterapLog formatter used in Tornado. Key features of this formatter are: * Color support when logging to a terminal that supports it. * Timestamps on every log line. * Robust against str/bytes encoding problems. This formatter is enabled automatically by `tornado.options.parse_command_line` or `tornado.options.parse_config_file` (unless ``--logging=none`` is used). Color support on Windows versions that do not support ANSI color codes is enabled by use of the colorama__ library. Applications that wish to use this must first initialize colorama with a call to ``colorama.init``. See the colorama documentation for details. __ https://pypi.python.org/pypi/colorama .. versionchanged:: 4.5 Added support for ``colorama``. Changed the constructor signature to be compatible with `logging.config.dictConfig`. zV%(color)s[%(levelname)1.1s %(asctime)s %(module)s:%(lineno)d]%(end_color)s %(message)sz%y%m%d %H:%M:%S%TN)fmtdatefmtstylecolorr r c Cstjj||d||_i|_|rtrtdurtdpDtdpDd}|D] \}}t t ||d|j|<qNtd} | durt | d|_ qd|_ q|D]\}}d ||j|<qd |_ nd|_ dS) aX :arg bool color: Enables color support. :arg str fmt: Log message format. It will be applied to the attributes dict of log records. The text between ``%(color)s`` and ``%(end_color)s`` will be colored depending on the level if color support is on. :arg dict colors: color mappings from logging level to terminal color code :arg str datefmt: Datetime format. Used for formatting ``(asctime)`` placeholder in ``prefix_fmt``. .. versionchanged:: 3.2 Added ``fmt`` and ``datefmt`` arguments. )r&NZsetafZsetfasciiZsgr0z[2;3%dmz) logging Formatter__init___fmt_colorsrrZtigetstritemsrZtparm_normal) selfr%r&r'r(r Zfg_colorlevelnocodenormalrrrr.ts$   zLogFormatter.__init__)recordr c Csz$|}t|tsJt||_Wn4tyX}zd||jf|_WYd}~n d}~00||tt |j |_ |j |j vr|j |j |_|j|_n d|_|_|j|j}|jr|js||j|_|jr|g}|dd|jdDd|}|ddS)NzBad message (%r): %rr+css|]}t|VqdSr)r).0lnrrr r)z&LogFormatter.format.. z ) getMessage isinstancerrmessager__dict__ formatTimerstrr&asctimer4r0r(r2Z end_colorr/exc_infoexc_textformatExceptionrstripextendsplitjoinreplace)r3r7r>e formattedlinesrrrformats(&      zLogFormatter.format)__name__ __module__ __qualname____doc__DEFAULT_FORMATZDEFAULT_DATE_FORMATr,DEBUGINFOWARNINGERRORCRITICALZDEFAULT_COLORSrAboolrintr.rrNrrrrrQs.   4r)optionsloggerr cCs|durddl}|jj}|jdus0|jdkr4dS|durDt}|tt|j|jr|j }|dkrtj j |j|j |j dd}n<|dkrtj j|j|j|j|j dd}nd d |}t||td d |||js|jdur|j st}|t||dS) zTurns on formatted logging output as configured. This is called automatically by `tornado.options.parse_command_line` and `tornado.options.parse_config_file`. Nrnonesizezutf-8)filenamemaxBytes backupCountencodingtime)r_whenintervalrarbz.The value of log_rotate_mode option should be z"size" or "time", not "%s".F)r()tornado.optionsr[r,lower getLoggersetLevelrupperlog_file_prefixlog_rotate_modehandlersRotatingFileHandlerlog_file_max_sizelog_file_num_backupsTimedRotatingFileHandlerlog_rotate_whenlog_rotate_interval ValueError setFormatterr addHandler log_to_stderr StreamHandler)r[r\tornadoZ rotate_modeZchannel error_messagerrrenable_pretty_loggingsH   r{)r[r csdurddl}|jjjdddddjdtdd d jd tdd d djdtddd jdtddd jdtddd jdtddd jdtddd fdddS) aBAdd logging-related flags to ``options``. These options are present automatically on the default options instance; this method is only necessary if you have created your own `.OptionParser`. .. versionadded:: 4.2 This function existed in prior versions but was broken and undocumented until 4.2. Nrr,infozSSet the Python log level. If 'none', tornado won't touch the logging configuration.zdebug|info|warning|error|none)defaulthelpmetavarrwzSend log output to stderr (colorized if possible). By default use stderr if --log_file_prefix is not set and no other logging is configured.)typer}r~rkPATHzPath prefix for log files. Note that if you are running multiple tornado processes, log_file_prefix must be different for each of them (e.g. include the port number))rr}rr~roiz%max size of log files before rolloverrp znumber of log files to keeprrZmidnightzcspecify the type of TimedRotatingFileHandler interval other options:('S', 'M', 'H', 'D', 'W0'-'W6')rsr"z$The interval value of timed rotatingrlr^z(The mode of rotating files(time or size)cstSr)r{rr[rrWr)z(define_logging_options..)rfr[ZdefinerYrArZZadd_parse_callback)r[ryrrrdefine_logging_options sd     r)NN)N)rRr,logging.handlersrZtornado.escaperZ tornado.utilrrr ImportErrorrtypingrrrrrhZ access_logZapp_logZgen_logrYrrArr-rLoggerr{rrrrrs6            2