HEX
Server: Apache
System: Linux nc-ph-4101.simplemoneygoals.com 5.14.0-503.21.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jan 12 09:45:05 EST 2025 x86_64
User: dailygoldindex (1004)
PHP: 8.1.33
Disabled: NONE
$ pwd: /lib64/python3.9/logging/__pycache__/
Upload Files
File: //lib64/python3.9/logging/__pycache__/handlers.cpython-39.pyc
a

�DOg��@szdZddlZddlZddlZddlZddlZddlZddlZddlm	Z	m
Z
mZddlZddl
Z
ddlZdZdZdZdZdZdZd	ZGd
d�dej�ZGdd
�d
e�ZGdd�de�ZGdd�dej�ZGdd�dej�ZGdd�de�ZGdd�dej�ZGdd�dej�ZGdd�dej�Z Gdd�dej�Z!Gdd�dej�Z"Gd d!�d!e"�Z#Gd"d#�d#ej�Z$Gd$d%�d%e%�Z&dS)&z�
Additional handlers for the logging package for Python. The core package is
based on PEP 282 and comments thereto in comp.lang.python.

Copyright (C) 2001-2021 Vinay Sajip. All Rights Reserved.

To use, simply 'import logging.handlers' and log away!
�N)�ST_DEV�ST_INO�ST_MTIMEi<#i=#i>#i?#i�Qc@s:eZdZdZdZdZddd�Zdd�Zdd	�Zd
d�Z	dS)
�BaseRotatingHandlerz�
    Base class for handlers that rotate log files at a certain point.
    Not meant to be instantiated directly.  Instead, use RotatingFileHandler
    or TimedRotatingFileHandler.
    NFcCs.tjj||||||d�||_||_||_dS)zA
        Use the specified filename for streamed logging
        ��mode�encoding�delay�errorsN)�logging�FileHandler�__init__rr	r��self�filenamerr	r
r�r�(/usr/lib64/python3.9/logging/handlers.pyr6s�zBaseRotatingHandler.__init__cCsFz$|�|�r|��tj�||�Wnty@|�|�Yn0dS)z�
        Emit a record.

        Output the record to the file, catering for rollover as described
        in doRollover().
        N)�shouldRollover�
doRolloverrr
�emit�	Exception�handleError�r�recordrrrrAs
zBaseRotatingHandler.emitcCst|j�s|}n
|�|�}|S)a�
        Modify the filename of a log file when rotating.

        This is provided so that a custom filename can be provided.

        The default implementation calls the 'namer' attribute of the
        handler, if it's callable, passing the default name to
        it. If the attribute isn't callable (the default is None), the name
        is returned unchanged.

        :param default_name: The default name for the log file.
        )�callable�namer)rZdefault_name�resultrrr�rotation_filenameOs

z%BaseRotatingHandler.rotation_filenamecCs4t|j�s$tj�|�r0t�||�n|�||�dS)aL
        When rotating, rotate the current log.

        The default implementation calls the 'rotator' attribute of the
        handler, if it's callable, passing the source and dest arguments to
        it. If the attribute isn't callable (the default is None), the source
        is simply renamed to the destination.

        :param source: The source filename. This is normally the base
                       filename, e.g. 'test.log'
        :param dest:   The destination filename. This is normally
                       what the source is rotated to, e.g. 'test.log.1'.
        N)r�rotator�os�path�exists�rename)r�source�destrrr�rotatebs
zBaseRotatingHandler.rotate)NFN)
�__name__�
__module__�__qualname__�__doc__rrrrrr&rrrrr-s
rc@s*eZdZdZddd�Zdd	�Zd
d�ZdS)
�RotatingFileHandlerz�
    Handler for logging to a set of files, which switches from one file
    to the next when the current file reaches a certain size.
    �arNFcCs2|dkrd}tj||||||d�||_||_dS)a�
        Open the specified file and use it as the stream for logging.

        By default, the file grows indefinitely. You can specify particular
        values of maxBytes and backupCount to allow the file to rollover at
        a predetermined size.

        Rollover occurs whenever the current log file is nearly maxBytes in
        length. If backupCount is >= 1, the system will successively create
        new files with the same pathname as the base file, but with extensions
        ".1", ".2" etc. appended to it. For example, with a backupCount of 5
        and a base file name of "app.log", you would get "app.log",
        "app.log.1", "app.log.2", ... through to "app.log.5". The file being
        written to is always "app.log" - when it gets filled up, it is closed
        and renamed to "app.log.1", and if files "app.log.1", "app.log.2" etc.
        exist, then they are renamed to "app.log.2", "app.log.3" etc.
        respectively.

        If maxBytes is zero, rollover never occurs.
        rr,�r	r
rN)rr�maxBytes�backupCount)rrrr.r/r	r
rrrrr|s�zRotatingFileHandler.__init__cCs�|jr|j��d|_|jdkr�t|jddd�D]^}|�d|j|f�}|�d|j|df�}tj�|�r2tj�|�r�t�	|�t�
||�q2|�|jd�}tj�|�r�t�	|�|�|j|�|js�|�
�|_dS)z<
        Do a rollover, as described in __init__().
        Nr����z%s.%dz.1)�stream�closer/�ranger�baseFilenamer r!r"�remover#r&r
�_open)r�iZsfn�dfnrrrr�s&


�

zRotatingFileHandler.doRollovercCsztj�|j�r tj�|j�s dS|jdur4|��|_|jdkrvd|�|�}|j�	dd�|j�
�t|�|jkrvdSdS)z�
        Determine if rollover should occur.

        Basically, see if the supplied record would cause the file to exceed
        the size limit we have.
        FNrz%s
�T)r r!r"r5�isfiler2r7r.�format�seek�tell�len�rr�msgrrrr�s


z"RotatingFileHandler.shouldRollover)r,rrNFN)r'r(r)r*rrrrrrrr+ws�
"r+c@s:eZdZdZddd�Zd	d
�Zdd�Zd
d�Zdd�ZdS)�TimedRotatingFileHandlerz�
    Handler for logging to a file, rotating the log file at certain timed
    intervals.

    If backupCount is > 0, when rollover is done, no more than backupCount
    files are kept - the oldest ones are deleted.
    �hr0rNFc
Cs�tj||d|||	d�|��|_||_||_||_|jdkrPd|_d|_d|_	n�|jdkrnd|_d	|_d
|_	n�|jdkr�d|_d
|_d|_	n�|jdks�|jdkr�d|_d|_d|_	n�|j�
d��r0d|_t|j�dkr�td|j��|jddk�s|jddk�rtd|j��t
|jd�|_d|_d|_	ntd|j��t�|j	tj�|_	|j||_|j}tj�|��r�t�|�t}
nt
t���}
|�|
�|_dS)Nr,r-�Sr0z%Y-%m-%d_%H-%M-%Sz-^\d{4}-\d{2}-\d{2}_\d{2}-\d{2}-\d{2}(\.\w+)?$�M�<z%Y-%m-%d_%H-%Mz'^\d{4}-\d{2}-\d{2}_\d{2}-\d{2}(\.\w+)?$�H�z%Y-%m-%d_%Hz!^\d{4}-\d{2}-\d{2}_\d{2}(\.\w+)?$�D�MIDNIGHTrz%Y-%m-%dz^\d{4}-\d{2}-\d{2}(\.\w+)?$�Wi�:	r:zHYou must specify a day for weekly rollover from 0 to 6 (0 is Monday): %s�0�6z-Invalid day specified for weekly rollover: %sz'Invalid rollover interval specified: %s)rr�upper�whenr/�utc�atTime�interval�suffix�extMatch�
startswithr?�
ValueError�int�	dayOfWeek�re�compile�ASCIIr5r r!r"�statr�time�computeRollover�
rolloverAt)rrrOrRr/r	r
rPrQr�trrrr�sP�



 z!TimedRotatingFileHandler.__init__cCsd||j}|jdks"|j�d��r`|jr4t�|�}n
t�|�}|d}|d}|d}|d}|jdurnt}n |jj	d|jj
d|jj}||d|d|}	|	d	kr�|	t7}	|d
d}||	}|j�d��r`|}
|
|jk�r`|
|jkr�|j|
}nd|
|jd
}||d}|j�s\|d
}
t�|�d
}|
|k�r\|
�sPd}nd}||7}|}|S)zI
        Work out the rollover time based on the specified time.
        rJrK����NrFrr0�rr1���rH)
rRrOrUrPr]�gmtime�	localtimerQ�	_MIDNIGHTZhourZminute�secondrX)r�currentTimerr`ZcurrentHourZ
currentMinuteZ
currentSecondZ
currentDayZ	rotate_ts�rZdayZ
daysToWait�
newRolloverAt�dstNow�
dstAtRollover�addendrrrr^sL


��

z(TimedRotatingFileHandler.computeRollovercCs>tj�|j�r tj�|j�s dStt���}||jkr:dSdS)z�
        Determine if rollover should occur.

        record is not used, as we are just comparing times, but it is needed so
        the method signatures are the same
        FT)r r!r"r5r;rWr]r_)rrr`rrrrUs
z'TimedRotatingFileHandler.shouldRolloverc
Cs$tj�|j�\}}t�|�}g}tj�|�\}}|d}t|�}|D]�}	|jdur`|	�|�s�qDn6|	�|�s�|	�	|�r�t|	�|dkr�|	|d�
�s�qD|	d|�|krD|	|d�}
|
�d�}|D](}|j�|�r�|�
tj�||	��qDq�qDt|�|jk�rg}n|��|dt|�|j�}|S)z�
        Determine the files to delete when rolling over.

        More specific than the earlier method, which just used glob.glob().
        �.Nr0)r r!�splitr5�listdir�splitextr?rrU�endswith�isdigitrT�match�append�joinr/�sort)
rZdirNameZbaseNameZ	fileNamesr�n�e�prefix�plenZfileNamerS�parts�partrrr�getFilesToDeleteds8


��
z)TimedRotatingFileHandler.getFilesToDeletecCsv|jr|j��d|_tt���}t�|�d}|j|j}|jrNt�|�}n6t�|�}|d}||kr�|rrd}nd}t�||�}|�	|j
dt�|j|��}t
j�|�r�t
�|�|�|j
|�|jdkr�|��D]}t
�|�q�|js�|��|_|�|�}	|	|k�r|	|j}	�q|jdk�s4|j�d��rl|j�slt�|	�d}
||
k�rl|�s`d}nd}|	|7}	|	|_dS)	ax
        do a rollover; in this case, a date/time stamp is appended to the filename
        when the rollover happens.  However, you want the file to be named for the
        start of the interval, not the current time.  If there is a backup count,
        then we have to get a list of matching filenames, sort them and remove
        the one with the oldest suffix.
        Nr1rHrfrqrrJrK)r2r3rWr]rhr_rRrPrgrr5�strftimerSr r!r"r6r&r/r�r
r7r^rOrU)rrkrnr`Z	timeTupleZdstThenrpr9�srmrorrrr�sJ

�




"
z#TimedRotatingFileHandler.doRollover)rCr0rNFFNN)	r'r(r)r*rr^rr�rrrrrrB�s�
<I*rBc@s2eZdZdZd
dd�Zdd�Zd	d
�Zdd�ZdS)�WatchedFileHandlera�
    A handler for logging to a file, which watches the file
    to see if it has changed while in use. This can happen because of
    usage of programs such as newsyslog and logrotate which perform
    log file rotation. This handler, intended for use under Unix,
    watches the file to see if it has changed since the last emit.
    (A file has changed if its device or inode have changed.)
    If it has changed, the old file stream is closed, and the file
    opened to get a new stream.

    This handler is not appropriate for use under Windows, because
    under Windows open files cannot be moved or renamed - logging
    opens the files with exclusive locks - and so there is no need
    for such a handler. Furthermore, ST_INO is not supported under
    Windows; stat always returns zero for this value.

    This handler is based on a suggestion and patch by Chad J.
    Schroeder.
    r,NFcCs0tjj||||||d�d\|_|_|��dS)Nr)r1r1)rr
r�dev�ino�_statstreamrrrrr�s�zWatchedFileHandler.__init__cCs0|jr,t�|j���}|t|t|_|_dS�N)r2r �fstat�filenorrr�r��rZsresrrrr��szWatchedFileHandler._statstreamcCs�zt�|j�}Wnty&d}Yn0|rH|t|jksH|t|jkr~|jdur~|j�	�|j�
�d|_|��|_|��dS)z�
        Reopen log file if needed.

        Checks if the underlying file has changed, and if it
        has, close the old stream and reopen the file to get the
        current stream.
        N)
r r\r5�FileNotFoundErrorrr�rr�r2�flushr3r7r�r�rrr�reopenIfNeeded�s
 



z!WatchedFileHandler.reopenIfNeededcCs|��tj�||�dS)z�
        Emit a record.

        If underlying file has changed, reopen the file before emitting the
        record to it.
        N)r�rr
rrrrrr�szWatchedFileHandler.emit)r,NFN)r'r(r)r*rr�r�rrrrrr��s�
r�c@sReZdZdZdd�Zddd�Zdd�Zd	d
�Zdd�Zd
d�Z	dd�Z
dd�ZdS)�
SocketHandlera
    A handler class which writes logging records, in pickle format, to
    a streaming socket. The socket is kept open across logging calls.
    If the peer resets it, an attempt is made to reconnect on the next call.
    The pickle which is sent is that of the LogRecord's attribute dictionary
    (__dict__), so that the receiver does not need to have the logging module
    installed in order to process the logging event.

    To unpickle the record at the receiving end into a LogRecord, use the
    makeLogRecord function.
    cCsZtj�|�||_||_|dur(||_n
||f|_d|_d|_d|_d|_	d|_
d|_dS)a
        Initializes the handler with a specific host address and port.

        When the attribute *closeOnError* is set to True - if a socket error
        occurs, the socket is silently closed and then reopened on the next
        logging call.
        NFg�?g>@g@)r�Handlerr�host�port�address�sock�closeOnError�	retryTime�
retryStart�retryMax�retryFactor�rr�r�rrrrs
zSocketHandler.__init__r0cCsh|jdurtj|j|d�}nHt�tjtj�}|�|�z|�|j�Wntyb|�	��Yn0|S)zr
        A factory method which allows subclasses to define the precise
        type of socket they want.
        N��timeout)
r��socket�create_connectionr��AF_UNIX�SOCK_STREAM�
settimeout�connect�OSErrorr3)rr�rrrr�
makeSocket.s

zSocketHandler.makeSocketcCs�t��}|jdurd}n
||jk}|r�z|��|_d|_WnTty�|jdur\|j|_n"|j|j|_|j|jkr~|j|_||j|_Yn0dS)z�
        Try to create a socket, using an exponential backoff with
        a max retry time. Thanks to Robert Olson for the original patch
        (SF #815911) which has been slightly refactored.
        NT)	r]r�r�r�r�r�ZretryPeriodr�r�)rZnowZattemptrrr�createSocket?s





zSocketHandler.createSocketcCsP|jdur|��|jrLz|j�|�Wn"tyJ|j��d|_Yn0dS)z�
        Send a pickled string to the socket.

        This function allows for partial sends which can happen when the
        network is busy.
        N)r�r��sendallr�r3�rr�rrr�send[s

zSocketHandler.sendcCsj|j}|r|�|�}t|j�}|��|d<d|d<d|d<|�dd�t�|d�}t�	dt
|��}||S)z�
        Pickles the record in binary format with a length prefix, and
        returns it ready for transmission across the socket.
        rAN�args�exc_info�messager0z>L)r�r<�dict�__dict__�
getMessage�pop�pickle�dumps�struct�packr?)rr�ei�dummy�dr�Zslenrrr�
makePicklens

zSocketHandler.makePicklecCs0|jr|jr|j��d|_ntj�||�dS)z�
        Handle an error during logging.

        An error has occurred during logging. Most likely cause -
        connection lost. Close the socket so that we can retry on the
        next event.
        N)r�r�r3rr�rrrrrr�s
zSocketHandler.handleErrorcCs:z|�|�}|�|�Wnty4|�|�Yn0dS)a
        Emit a record.

        Pickles the record and writes it to the socket in binary format.
        If there is an error with the socket, silently drop the packet.
        If there was a problem with the socket, re-establishes the
        socket.
        N)r�r�rr)rrr�rrrr�s
	
zSocketHandler.emitcCsH|��z0|j}|r"d|_|��tj�|�W|��n
|��0dS�z$
        Closes the socket.
        N)�acquirer�r3rr��release)rr�rrrr3�szSocketHandler.closeN)r0)r'r(r)r*rr�r�r�r�rrr3rrrrr�s
r�c@s(eZdZdZdd�Zdd�Zdd�ZdS)	�DatagramHandlera�
    A handler class which writes logging records, in pickle format, to
    a datagram socket.  The pickle which is sent is that of the LogRecord's
    attribute dictionary (__dict__), so that the receiver does not need to
    have the logging module installed in order to process the logging event.

    To unpickle the record at the receiving end into a LogRecord, use the
    makeLogRecord function.

    cCst�|||�d|_dS)zP
        Initializes the handler with a specific host address and port.
        FN)r�rr�r�rrrr�szDatagramHandler.__init__cCs*|jdurtj}ntj}t�|tj�}|S)zu
        The factory method of SocketHandler is here overridden to create
        a UDP socket (SOCK_DGRAM).
        N)r�r�r��AF_INET�
SOCK_DGRAM)r�familyr�rrrr��s

zDatagramHandler.makeSocketcCs&|jdur|��|j�||j�dS)z�
        Send a pickled string to a socket.

        This function no longer allows for partial sends which can happen
        when the network is busy - UDP does not guarantee delivery and
        can deliver packets out of sequence.
        N)r�r��sendtor�r�rrrr��s
zDatagramHandler.sendN)r'r(r)r*rr�r�rrrrr��s
r�c@s8eZdZdZdZdZdZdZdZdZ	dZ
d	ZdZdZ
dZdZdZdZdZd	Zd
ZdZdZd
ZdZdZdZdZdZdZdZdZdZ dZ!dZ"dZ#eeeeeeee
e	eeed�Z$eeeeeeeeeeeeeee
eeeeee e!e"e#d�Z%ddddd d!�Z&d"e'fe
d#fd$d%�Z(d&d'�Z)d(d)�Z*d*d+�Z+d,d-�Z,d.Z-d/Z.d0d1�Z/d#S)2�
SysLogHandlera
    A handler class which sends formatted logging records to a syslog
    server. Based on Sam Rushing's syslog module:
    http://www.nightmare.com/squirl/python-ext/misc/syslog.py
    Contributed by Nicolas Untz (after which minor refactoring changes
    have been made).
    rr0r:rarbrcrdre��	�
���
����������)ZalertZcrit�critical�debugZemerg�err�error�infoZnoticeZpanic�warn�warning)ZauthZauthprivZconsoleZcron�daemon�ftpZkernZlprZmail�newsZntpZsecurityzsolaris-cronZsyslog�userZuucpZlocal0Zlocal1Zlocal2Zlocal3Zlocal4Zlocal5Zlocal6Zlocal7r�r�r�r�r�)�DEBUG�INFO�WARNING�ERROR�CRITICAL�	localhostNcCs2tj�|�||_||_||_t|t�rRd|_z|�	|�Wnt
yNYn0n�d|_|durftj}|\}}t�
||d|�}|s�t
d��|D]�}|\}}}	}
}d}}
z.t�|||	�}
|tjkr�|
�|�W�qWq�t
�y}z |}|
dur�|
��WYd}~q�d}~00q�|du�r"|�|
|_||_dS)a
        Initialize a handler.

        If address is specified as a string, a UNIX socket is used. To log to a
        local syslogd, "SysLogHandler(address="/dev/log")" can be used.
        If facility is not specified, LOG_USER is used. If socktype is
        specified as socket.SOCK_DGRAM or socket.SOCK_STREAM, that specific
        socket type will be used. For Unix sockets, you can also specify a
        socktype of None, in which case socket.SOCK_DGRAM will be used, falling
        back to socket.SOCK_STREAM.
        TFNrz!getaddrinfo returns an empty list)rr�rr��facility�socktype�
isinstance�str�
unixsocket�_connect_unixsocketr�r�r��getaddrinfor�r�r3)rr�r�r�r�r�Zress�res�af�proto�_�sar�r��excrrrrGsB



 
zSysLogHandler.__init__cCs�|j}|durtj}t�tj|�|_z|j�|�||_Wntty�|j��|jdur^�tj}t�tj|�|_z|j�|�||_Wnty�|j���Yn0Yn0dSr�)r�r�r�r�r�r�r3r�)rr�Zuse_socktyperrrr�}s&




z!SysLogHandler._connect_unixsocketcCs4t|t�r|j|}t|t�r(|j|}|d>|BS)z�
        Encode the facility and priority. You can pass in strings or
        integers - if strings are passed, the facility_names and
        priority_names mapping dictionaries are used to convert them to
        integers.
        ra)r�r��facility_names�priority_names)rr��priorityrrr�encodePriority�s




zSysLogHandler.encodePrioritycCs:|��z"|j��tj�|�W|��n
|��0dSr�)r�r�r3rr�r��rrrrr3�s

zSysLogHandler.closecCs|j�|d�S)aK
        Map a logging level name to a key in the priority_names map.
        This is useful in two scenarios: when custom levels are being
        used, and in the case where you can't do a straightforward
        mapping by lowercasing the logging level name because of locale-
        specific issues (see SF #1524081).
        r�)�priority_map�get)r�	levelNamerrr�mapPriority�szSysLogHandler.mapPriority�TcCs�z�|�|�}|jr|j|}|jr*|d7}d|�|j|�|j��}|�d�}|�d�}||}|jr�z|j	�
|�Wq�ty�|j	��|�
|j�|j	�
|�Yq�0n*|jt	jkr�|j	�||j�n|j	�|�Wnty�|�|�Yn0dS)z�
        Emit a record.

        The record is formatted, and then sent to the syslog server. If
        exception information is present, it is NOT sent to the server.
        �z<%d>�utf-8N)r<�ident�
append_nulr�r�r��	levelname�encoder�r�r�r�r3r�r�r�r�r�r�rr)rrrAZpriorrrr�s0



�


zSysLogHandler.emit)0r'r(r)r*Z	LOG_EMERGZ	LOG_ALERTZLOG_CRITZLOG_ERRZLOG_WARNINGZ
LOG_NOTICEZLOG_INFOZ	LOG_DEBUGZLOG_KERNZLOG_USERZLOG_MAILZ
LOG_DAEMONZLOG_AUTHZ
LOG_SYSLOGZLOG_LPRZLOG_NEWSZLOG_UUCPZLOG_CRONZLOG_AUTHPRIVZLOG_FTPZLOG_NTPZLOG_SECURITYZLOG_CONSOLEZLOG_SOLCRONZ
LOG_LOCAL0Z
LOG_LOCAL1Z
LOG_LOCAL2Z
LOG_LOCAL3Z
LOG_LOCAL4Z
LOG_LOCAL5Z
LOG_LOCAL6Z
LOG_LOCAL7r�r�r��SYSLOG_UDP_PORTrr�r�r3r�r�r�rrrrrr��s��� ��
6

r�c@s*eZdZdZd
dd�Zdd�Zdd	�ZdS)�SMTPHandlerzK
    A handler class which sends an SMTP email for each logging event.
    N�@cCs�tj�|�t|ttf�r(|\|_|_n|d|_|_t|ttf�rR|\|_|_	nd|_||_
t|t�rn|g}||_||_
||_||_dS)ax
        Initialize the handler.

        Initialize the instance with the from and to addresses and subject
        line of the email. To specify a non-standard SMTP port, use the
        (host, port) tuple format for the mailhost argument. To specify
        authentication credentials, supply a (username, password) tuple
        for the credentials argument. To specify the use of a secure
        protocol (TLS), pass in a tuple for the secure argument. This will
        only be used when authentication credentials are supplied. The tuple
        will be either an empty tuple, or a single-value tuple with the name
        of a keyfile, or a 2-value tuple with the names of the keyfile and
        certificate file. (This tuple is passed to the `starttls` method).
        A timeout in seconds can be specified for the SMTP connection (the
        default is one second).
        N)rr�rr��list�tuple�mailhost�mailport�username�password�fromaddrr��toaddrs�subject�securer�)rrrr	r
�credentialsrr�rrrr�s
zSMTPHandler.__init__cCs|jS)z�
        Determine the subject for the email.

        If you want to specify a subject line which is record-dependent,
        override this method.
        )r
rrrr�
getSubjectszSMTPHandler.getSubjectcCsz�ddl}ddlm}ddl}|j}|s.|j}|j|j||jd�}|�}|j	|d<d�
|j�|d<|�|�|d<|j
��|d	<|�|�|��|jr�|jdur�|��|j|j�|��|�|j|j�|�|�|��Wnty�|�|�Yn0dS)
zd
        Emit a record.

        Format the record and send it to the specified addressees.
        rN)�EmailMessager�ZFrom�,ZToZSubjectZDate)�smtplibZ
email.messagerZemail.utilsrZ	SMTP_PORTZSMTPrr�rryr	r
ZutilsrhZset_contentr<rrZehloZstarttlsZloginrZsend_message�quitrr)rrrrZemailr�ZsmtprArrrrs0


zSMTPHandler.emit)NNr)r'r(r)r*rr
rrrrrr�s
�
#	rc@sBeZdZdZddd�Zdd�Zdd	�Zd
d�Zdd
�Zdd�Z	dS)�NTEventLogHandlera�
    A handler class which sends events to the NT Event Log. Adds a
    registry entry for the specified application name. If no dllname is
    provided, win32service.pyd (which contains some basic message
    placeholders) is used. Note that use of these placeholders will make
    your event logs big, as the entire message source is held in the log.
    If you want slimmer logs, you have to pass in the name of your own DLL
    which contains the message definitions you want to use in the event log.
    N�Applicationc
Cs�tj�|�z�ddl}ddl}||_||_|s`tj�	|jj
�}tj�	|d�}tj�|dd�}||_||_
|j�|||�|j|_tj|jtj|jtj|jtj|jtj|ji|_Wn ty�td�d|_Yn0dS)Nrzwin32service.pydzWThe Python Win32 extensions for NT (service, event logging) appear not to be available.)rr�r�win32evtlogutil�win32evtlog�appname�_welur r!rr�__file__ry�dllname�logtypeZAddSourceToRegistryZEVENTLOG_ERROR_TYPE�deftyper�ZEVENTLOG_INFORMATION_TYPEr�r�ZEVENTLOG_WARNING_TYPEr�r��typemap�ImportError�print)rrrrrrrrrr8s,�
zNTEventLogHandler.__init__cCsdS)ay
        Return the message ID for the event record. If you are using your
        own messages, you could do this by having the msg passed to the
        logger being an ID rather than a formatting string. Then, in here,
        you could use a dictionary lookup to get the message ID. This
        version returns 1, which is the base message ID in win32service.pyd.
        r0rrrrr�getMessageIDRszNTEventLogHandler.getMessageIDcCsdS)z�
        Return the event category for the record.

        Override this if you want to specify your own categories. This version
        returns 0.
        rrrrrr�getEventCategory\sz"NTEventLogHandler.getEventCategorycCs|j�|j|j�S)a�
        Return the event type for the record.

        Override this if you want to specify your own types. This version does
        a mapping using the handler's typemap attribute, which is set up in
        __init__() to a dictionary which contains mappings for DEBUG, INFO,
        WARNING, ERROR and CRITICAL. If you are using your own levels you will
        either need to override this method or place a suitable dictionary in
        the handler's typemap attribute.
        )rr��levelnorrrrr�getEventTypeeszNTEventLogHandler.getEventTypecCsl|jrhzD|�|�}|�|�}|�|�}|�|�}|j�|j||||g�Wntyf|�|�Yn0dS)z�
        Emit a record.

        Determine the message ID, event category and event type. Then
        log the message in the NT event log.
        N)	rrr r"r<ZReportEventrrr)rr�id�cat�typerArrrrrs



zNTEventLogHandler.emitcCstj�|�dS)aS
        Clean up this handler.

        You can remove the application name from the registry as a
        source of event log entries. However, if you do this, you will
        not be able to see the events as you intended in the Event Log
        Viewer - it needs to be able to access the registry to get the
        DLL name.
        N)rr�r3r�rrrr3�szNTEventLogHandler.close)Nr)
r'r(r)r*rrr r"rr3rrrrr.s	

	
rc@s2eZdZdZd
dd�Zdd�Zd	d
�Zdd�ZdS)�HTTPHandlerz^
    A class which sends records to a Web server, using either GET or
    POST semantics.
    �GETFNcCs`tj�|�|��}|dvr$td��|s8|dur8td��||_||_||_||_||_	||_
dS)zr
        Initialize the instance with the host, the request URL, and the method
        ("GET" or "POST")
        )r'�POSTzmethod must be GET or POSTNz3context parameter only makes sense with secure=True)rr�rrNrVr��url�methodrr�context)rr�r)r*rrr+rrrr�szHTTPHandler.__init__cCs|jS)z�
        Default implementation of mapping the log record into a dict
        that is sent as the CGI data. Overwrite in your class.
        Contributed by Franz Glasner.
        )r�rrrr�mapLogRecord�szHTTPHandler.mapLogRecordcCs0ddl}|r |jj||jd�}n|j�|�}|S)z�
        get a HTTP[S]Connection.

        Override when a custom connection is required, for example if
        there is a proxy.
        rN)r+)Zhttp.client�clientZHTTPSConnectionr+ZHTTPConnection)rr�r�http�
connectionrrr�
getConnection�s
zHTTPHandler.getConnectioncCsV�z0ddl}|j}|�||j�}|j}|j�|�|��}|jdkrj|�	d�dkrVd}nd}|d||f}|�
|j|�|�	d�}|dkr�|d|�}|jdkr�|�d	d
�|�dtt
|���|j�rddl}	d|j�d
�}
d|	�|
����d�}
|�d|
�|��|jdk�r(|�|�d
��|��Wnt�yP|�|�Yn0dS)zk
        Emit a record.

        Send the record to the Web server as a percent-encoded dictionary
        rNr'�?�&z%c%s�:r(zContent-typez!application/x-www-form-urlencodedzContent-lengthz%s:%sr�zBasic �asciiZ
Authorization)�urllib.parser�r0rr)�parse�	urlencoder,r*�findZ
putrequestZ	putheaderr�r?r�base64r�Z	b64encode�strip�decodeZ
endheadersr�Zgetresponserr)rr�urllibr�rCr)�data�sepr8r9r�rrrr�s>


�zHTTPHandler.emit)r'FNN)r'r(r)r*rr,r0rrrrrr&�s�
r&c@s8eZdZdZdd�Zdd�Zdd�Zdd	�Zd
d�ZdS)
�BufferingHandlerz�
  A handler class which buffers logging records in memory. Whenever each
  record is added to the buffer, a check is made to see if the buffer should
  be flushed. If it should, then flush() is expected to do what's needed.
    cCstj�|�||_g|_dS)z>
        Initialize the handler with the buffer size.
        N)rr�r�capacity�buffer)rr@rrrr�szBufferingHandler.__init__cCst|j�|jkS)z�
        Should the handler flush its buffer?

        Returns true if the buffer is up to capacity. This method can be
        overridden to implement custom flushing strategies.
        )r?rAr@rrrr�shouldFlush�szBufferingHandler.shouldFlushcCs"|j�|�|�|�r|��dS)z�
        Emit a record.

        Append the record. If shouldFlush() tells us to, call flush() to process
        the buffer.
        N)rArxrBr�rrrrrs
zBufferingHandler.emitcCs.|��z|j��W|��n
|��0dS)zw
        Override to implement custom flushing behaviour.

        This version just zaps the buffer to empty.
        N)r�rA�clearr�r�rrrr�szBufferingHandler.flushc	Cs,z|��Wtj�|�ntj�|�0dS)zp
        Close the handler.

        This version just flushes and chains to the parent class' close().
        N)r�rr�r3r�rrrr3s
zBufferingHandler.closeN)	r'r(r)r*rrBrr�r3rrrrr?�s	r?c@sBeZdZdZejddfdd�Zdd�Zdd	�Zd
d�Z	dd
�Z
dS)�
MemoryHandlerz�
    A handler class which buffers logging records in memory, periodically
    flushing them to a target handler. Flushing occurs whenever the buffer
    is full, or when an event of a certain severity or greater is seen.
    NTcCs"t�||�||_||_||_dS)a;
        Initialize the handler with the buffer size, the level at which
        flushing should occur and an optional target.

        Note that without a target being set either here or via setTarget(),
        a MemoryHandler is no use to anyone!

        The ``flushOnClose`` argument is ``True`` for backward compatibility
        reasons - the old behaviour is that when the handler is closed, the
        buffer is flushed, even if the flush level hasn't been exceeded nor the
        capacity exceeded. To prevent this, set ``flushOnClose`` to ``False``.
        N)r?r�
flushLevel�target�flushOnClose)rr@rErFrGrrrr)szMemoryHandler.__init__cCst|j�|jkp|j|jkS)zP
        Check for buffer full or a record at the flushLevel or higher.
        )r?rAr@r!rErrrrrB=s
�zMemoryHandler.shouldFlushcCs*|��z||_W|��n
|��0dS)z:
        Set the target handler for this handler.
        N)r�rFr�)rrFrrr�	setTargetDszMemoryHandler.setTargetcCsL|��z4|jr2|jD]}|j�|�q|j��W|��n
|��0dS)z�
        For a MemoryHandler, flushing means just sending the buffered
        records to the target, if there is one. Override if you want
        different behaviour.

        The record buffer is also cleared by this operation.
        N)r�rFrA�handlerCr�rrrrr�Ns
zMemoryHandler.flushcCszzB|jr|��W|��zd|_t�|�W|��qv|��0n2|��zd|_t�|�W|��n
|��00dS)zi
        Flush, if appropriately configured, set the target to None and lose the
        buffer.
        N)rGr�r�rFr?r3r�r�rrrr3_s
�zMemoryHandler.close)r'r(r)r*rr�rrBrHr�r3rrrrrD#s�

rDc@s0eZdZdZdd�Zdd�Zdd�Zdd	�Zd
S)�QueueHandlera�
    This handler sends events to a queue. Typically, it would be used together
    with a multiprocessing Queue to centralise logging to file in one process
    (in a multi-process application), so as to avoid file write contention
    between processes.

    This code is new in Python 3.2, but this class can be copy pasted into
    user code for use with earlier Python versions.
    cCstj�|�||_dS)zA
        Initialise an instance, using the passed queue.
        N)rr�r�queue)rrKrrrr{szQueueHandler.__init__cCs|j�|�dS)z�
        Enqueue a record.

        The base implementation uses put_nowait. You may want to override
        this method if you want to use blocking, timeouts or custom queue
        implementations.
        N)rK�
put_nowaitrrrr�enqueue�szQueueHandler.enqueuecCs6|�|�}t�|�}||_||_d|_d|_d|_|S)a�
        Prepares a record for queuing. The object returned by this method is
        enqueued.

        The base implementation formats the record to merge the message
        and arguments, and removes unpickleable items from the record
        in-place.

        You might want to override this method if you want to convert
        the record to a dict or JSON string, or send a modified copy
        of the record while leaving the original intact.
        N)r<�copyr�rAr�r��exc_textr@rrr�prepare�s

zQueueHandler.preparecCs6z|�|�|��Wnty0|�|�Yn0dS)zm
        Emit a record.

        Writes the LogRecord to the queue, preparing it for pickling first.
        N)rMrPrrrrrrr�szQueueHandler.emitN)r'r(r)r*rrMrPrrrrrrJps


rJc@sZeZdZdZdZdd�dd�Zdd�Zd	d
�Zdd�Zd
d�Z	dd�Z
dd�Zdd�ZdS)�
QueueListenerz�
    This class implements an internal threaded listener which watches for
    LogRecords being added to a queue, removes them and passes them to a
    list of handlers for processing.
    NF)�respect_handler_levelcGs||_||_d|_||_dS)zW
        Initialise an instance with the specified queue and
        handlers.
        N)rK�handlers�_threadrR)rrKrRrSrrrr�szQueueListener.__init__cCs|j�|�S)z�
        Dequeue a record and return it, optionally blocking.

        The base implementation uses get. You may want to override this method
        if you want to use timeouts or work with custom queue implementations.
        )rKr�)r�blockrrr�dequeue�szQueueListener.dequeuecCs&tj|jd�|_}d|_|��dS)z�
        Start the listener.

        This starts up a background thread to monitor the queue for
        LogRecords to process.
        )rFTN)�	threading�Thread�_monitorrTr��start)rr`rrrrZ�szQueueListener.startcCs|S)a
        Prepare a record for handling.

        This method just returns the passed-in record. You may want to
        override this method if you need to do any custom marshalling or
        manipulation of the record before passing it to the handlers.
        rrrrrrP�szQueueListener.preparecCs@|�|�}|jD]*}|js d}n|j|jk}|r|�|�qdS)z|
        Handle a record.

        This just loops through the handlers offering them the record
        to handle.
        TN)rPrSrRr!�levelrI)rr�handler�processrrrrI�s

zQueueListener.handlecCsn|j}t|d�}z>|�d�}||jur6|r2|��Wqj|�|�|rL|��WqtjyfYqjYq0qdS)z�
        Monitor the queue for records, and ask the handler
        to deal with them.

        This method runs on a separate, internal thread.
        The thread will terminate if it sees a sentinel object in the queue.
        �	task_doneTN)rK�hasattrrV�	_sentinelr^rI�Empty)r�qZ
has_task_donerrrrrY�s



zQueueListener._monitorcCs|j�|j�dS)z�
        This is used to enqueue the sentinel record.

        The base implementation uses put_nowait. You may want to override this
        method if you want to use timeouts or work with custom queue
        implementations.
        N)rKrLr`r�rrr�enqueue_sentinelszQueueListener.enqueue_sentinelcCs|��|j��d|_dS)a

        Stop the listener.

        This asks the thread to terminate, and then waits for it to do so.
        Note that if you don't call this before your application exits, there
        may be some records still left on the queue, which won't be processed.
        N)rcrTryr�rrr�stops
zQueueListener.stop)
r'r(r)r*r`rrVrZrPrIrYrcrdrrrrrQ�s
	

rQ)'r*rr�r r�r�r]rYr\rrrrKrWrNZDEFAULT_TCP_LOGGING_PORTZDEFAULT_UDP_LOGGING_PORTZDEFAULT_HTTP_LOGGING_PORTZDEFAULT_SOAP_LOGGING_PORTr�ZSYSLOG_TCP_PORTrir
rr+rBr�r�r�r�r�rrr&r?rDrJ�objectrQrrrr�<module>s<	8JQyH(*PbZ9ME
@ Telegram