a 4jx@sdddlmZmZddlmZddlZddlZddlZGdddeZ GdddeZ e Z dd Z dS) )absolute_importprint_function)BufferingHandlerNc@s eZdZdZddZddZdS) RecordFilterz]Implement logging record filtering as per the configuration --logging-filter option. cCsRt|_t|_|dD]2}|ddkr@|j|ddq|j|qdS)N,r-)setincludeexcludesplitadd)selfnamesnamer8E:\soccer\ml_env\Lib\site-packages\behave/log_capture.py__init__s  zRecordFilter.__init__cCs|jr|j|jvS|j|jvSN)r rr )rrecordrrrfilters zRecordFilter.filterN)__name__ __module__ __qualname____doc__rrrrrrr s rc@sZeZdZdZdddZddZddZd d Zd d Zd dZ ddZ ddZ ddZ dS)LoggingCaptureaCapture logging events in a memory buffer for later display or query. Captured logging events are stored on the attribute :attr:`~LoggingCapture.buffer`: .. attribute:: buffer This is a list of captured logging events as `logging.LogRecords`_. .. _`logging.LogRecords`: http://docs.python.org/library/logging.html#logrecord-objects By default the format of the messages will be:: '%(levelname)s:%(name)s:%(message)s' This may be overridden using standard logging formatter names in the configuration variable ``logging_format``. The level of logging captured is set to ``logging.NOTSET`` by default. You may override this using the configuration setting ``logging_level`` (which is set to a level name.) Finally there may be `filtering of logging events`__ specified by the configuration variable ``logging_filter``. .. __: behave.html#command-line-arguments NcCst|d||_g|_d|_d}}|jr4|j}nd}|jrD|j}t||}| ||durj||_ n|j rz|j |_ ntj |_ |j r|t|j dS)Niz"%(levelname)s:%(name)s:%(message)s)rrconfig old_handlers old_levelZlogging_formatZlogging_datefmtlogging Formatter setFormatterlevelZ logging_levelNOTSETZlogging_filter addFilterr)rrr"Z log_formatdatefmt formatterrrrr<s&    zLoggingCapture.__init__cCs t|jSr)boolbufferrrrr__bool__YszLoggingCapture.__bool__cCsdSrrr)rrrflush\szLoggingCapture.flushcCs g|_dSr)r(r)rrrtruncate_szLoggingCapture.truncatecsdfddjDS)N c3s|]}j|VqdSr)r&format).0rr)rr cz*LoggingCapture.getvalue..)joinr(r)rr)rgetvaluebszLoggingCapture.getvaluecCs2t|}|jD]}||durdSqdS)zSearch through the buffer for a message that matches the given regular expression. Returns boolean indicating whether a match was found. NTF)recompiler(search getMessage)rpatternrrrr find_eventes   zLoggingCapture.find_eventcCstdd|jDS)zSearch through the buffer for any ERROR or CRITICAL events. Returns boolean indicating whether a match was found. css|]}|jdvr|VqdS))ERRORCRITICALN) levelname)r/rrrrr1vs z,LoggingCapture.any_errors..)anyr(r)rrr any_errorsqszLoggingCapture.any_errorscCst}|jjrTtjjjD]4}t|dr|j D]}|j ||f| |q2q|j ddD]>}t |tr~|j |qb|jjrb|j ||f| |qb|||j|_||jdS)aNTurn on logging capture by replacing all existing handlers configured in the logging module. If the config var logging_clear_handlers is set then we also remove all existing handlers. We also set the level of the root logger. The opposite of this is :meth:`~LoggingCapture.abandon`. handlersN)r getLoggerrlogging_clear_handlersLoggermanager loggerDictvalueshasattrr@rappend removeHandler isinstancerremove addHandlerr"rsetLevel)r root_loggerloggerhandlerrrrinveigleys      zLoggingCapture.inveiglecCsrt}|jddD]}||ur|j|q|jjrR|jD]\}}||q>|jdurn| |jd|_dS)zTurn off logging capture. If other handlers were removed by :meth:`~LoggingCapture.inveigle` then they are reinstated. N) rrAr@rKrrBrrLrrM)rrNrPrOrrrabandons   zLoggingCapture.abandon)N) rrrrrr*r+r,r4r:r?rQrRrrrrrs  #rcOs2ddd}|s"tj||ddS||dSdS)aDecorator to wrap an *environment file function* in log file capture. It configures the logging capture using the *behave* context - the first argument to the function being decorated (so don't use this to decorate something that doesn't have *context* as the first argument.) The basic usage is: .. code-block: python @capture def after_scenario(context, scenario): ... The function prints any captured logging (at the level determined by the ``log_level`` configuration setting) directly to stdout, regardless of error conditions. It is mostly useful for debugging in situations where you are seeing a message like:: No handlers could be found for logger "name" The decorator takes an optional "level" keyword argument which limits the level of logging captured, overriding the level in the run's configuration: .. code-block: python @capture(level=logging.ERROR) def after_scenario(context, scenario): ... This would limit the logging captured to just ERROR and above, and thus only display logged events if they are interesting. Ncsfdd}|S)Ncs^t|jd}|z|g|RW|n |0|}|rZtdt|dS)Nr"zCaptured Logging:)rrrQrRr4print)contextargshvfuncr"rrfsz,capture..create_decorator..fr)rZr"r[rrYrcreate_decorators z!capture..create_decoratorr"rSr)N) functoolspartialget)rVkwr\rrrcaptures$ ra) __future__rrlogging.handlersrrr]r5objectrr MemoryHandlerrarrrrs