OwlCyberSecurity - MANAGER
Edit File: _policybase.cpython-38.opt-1.pyc
U e5d�: � @ s� d Z ddlZddlmZ ddlmZ ddlmZ dddgZG d d � d �Z d d � Z d d� Z G dd� de ej d�Z e G dd� de ��Ze� ZdS )zwPolicy framework for the email package. Allows fine grained feature control of how the package parses and emits data. � N)�header)�charset)�_has_surrogates�Policy�Compat32�compat32c s@ e Zd ZdZ� fdd�Zdd� Zdd� Zdd � Zd d � Z� Z S ) � _PolicyBasea� Policy Object basic framework. This class is useless unless subclassed. A subclass should define class attributes with defaults for any values that are to be managed by the Policy object. The constructor will then allow non-default values to be set for these attributes at instance creation time. The instance will be callable, taking these same attributes keyword arguments, and returning a new instance identical to the called instance except for those values changed by the keyword arguments. Instances may be added, yielding new instances with any non-default values from the right hand operand overriding those in the left hand operand. That is, A + B == A(<non-default values of B>) The repr of an instance can be used to reconstruct the object if and only if the repr of the values can be used to reconstruct those values. c sH |� � D ]:\}}t| |�r.tt| ��||� qtd�|| jj���qdS )z�Create new Policy, possibly overriding some defaults. See class docstring for a list of overridable attributes. �*{!r} is an invalid keyword argument for {}N) �items�hasattr�superr � __setattr__� TypeError�format� __class__�__name__)�self�kw�name�value�r � �)/usr/lib64/python3.8/email/_policybase.py�__init__) s ��z_PolicyBase.__init__c C s* dd� | j �� D �}d�| jjd�|��S )Nc S s g | ]\}}d � ||��qS )z{}={!r})r )�.0r r r r r � <listcomp>8 s �z(_PolicyBase.__repr__.<locals>.<listcomp>z{}({})z, )�__dict__r r r r �join)r �argsr r r �__repr__7 s �z_PolicyBase.__repr__c K sr | j �| j �}| j�� D ]\}}t�|||� q|�� D ]4\}}t| |�s^td�|| j j ���t�|||� q8|S )z�Return a new instance with specified attributes changed. The new instance has the same attribute values as the current object, except for the changes passed in as keyword arguments. r ) r �__new__r r �objectr r r r r )r r Z newpolicy�attrr r r r �clone< s ��z_PolicyBase.clonec C s, t | |�rd}nd}t|�| jj|���d S )Nz'{!r} object attribute {!r} is read-onlyz!{!r} object has no attribute {!r})r �AttributeErrorr r r )r r r �msgr r r r N s z_PolicyBase.__setattr__c C s | j f |j�S )z�Non-default values from right operand override those from left. The object returned is a new instance of the subclass. )r# r )r �otherr r r �__add__U s z_PolicyBase.__add__) r � __module__� __qualname__�__doc__r r r# r r' � __classcell__r r r r r s r c C s, | � dd�d } |�dd�d }| d | S )N� � r )�rsplit�split)�docZ added_docr r r � _append_doc^ s r1 c C s� | j r(| j �d�r(t| jd j | j �| _ | j�� D ]V\}}|j r2|j �d�r2dd� | jD �D ]*}tt||�d�}|r\t||j �|_ q2q\q2| S )N�+r c s s | ]}|� � D ] }|V qqd S )N)�mro)r �base�cr r r � <genexpr>h s z%_extend_docstrings.<locals>.<genexpr>r* )r* � startswithr1 � __bases__r r �getattr)�clsr r" r5 r0 r r r �_extend_docstringsc s r; c @ s� e Zd ZdZdZdZdZdZdZdZ dd� Z d d � Z d d � Z e jd d� �Ze jdd� �Ze jdd� �Ze jdd� �Ze jdd� �ZdS )r aI Controls for how messages are interpreted and formatted. Most of the classes and many of the methods in the email package accept Policy objects as parameters. A Policy object contains a set of values and functions that control how input is interpreted and how output is rendered. For example, the parameter 'raise_on_defect' controls whether or not an RFC violation results in an error being raised or not, while 'max_line_length' controls the maximum length of output lines when a Message is serialized. Any valid attribute may be overridden when a Policy is created by passing it as a keyword argument to the constructor. Policy objects are immutable, but a new Policy object can be created with only certain values changed by calling the Policy instance with keyword arguments. Policy objects can also be added, producing a new Policy object in which the non-default attributes set in the right hand operand overwrite those specified in the left operand. Settable attributes: raise_on_defect -- If true, then defects should be raised as errors. Default: False. linesep -- string containing the value to use as separation between output lines. Default '\n'. cte_type -- Type of allowed content transfer encodings 7bit -- ASCII only 8bit -- Content-Transfer-Encoding: 8bit is allowed Default: 8bit. Also controls the disposition of (RFC invalid) binary data in headers; see the documentation of the binary_fold method. max_line_length -- maximum length of lines, excluding 'linesep', during serialization. None or 0 means no line wrapping is done. Default is 78. mangle_from_ -- a flag that, when True escapes From_ lines in the body of the message by putting a `>' in front of them. This is used when the message is being serialized by a generator. Default: True. message_factory -- the class to use to create new message objects. If the value is None, the default is Message. Fr, Z8bit�N Nc C s | j r |�| �||� dS )aZ Based on policy, either raise defect or call register_defect. handle_defect(obj, defect) defect should be a Defect subclass, but in any case must be an Exception subclass. obj is the object on which the defect should be registered if it is not raised. If the raise_on_defect is True, the defect is raised as an error, otherwise the object and the defect are passed to register_defect. This method is intended to be called by parsers that discover defects. The email package parsers always call it with Defect instances. N)�raise_on_defect�register_defect�r �objZdefectr r r � handle_defect� s zPolicy.handle_defectc C s |j �|� dS )a� Record 'defect' on 'obj'. Called by handle_defect if raise_on_defect is False. This method is part of the Policy API so that Policy subclasses can implement custom defect handling. The default implementation calls the append method of the defects attribute of obj. The objects used by the email package by default that get passed to this method will always have a defects attribute with an append method. N)Zdefects�appendr? r r r r> � s zPolicy.register_defectc C s dS )a[ Return the maximum allowed number of headers named 'name'. Called when a header is added to a Message object. If the returned value is not 0 or None, and there are already a number of headers with the name 'name' equal to the value returned, a ValueError is raised. Because the default behavior of Message's __setitem__ is to append the value to the list of headers, it is easy to create duplicate headers without realizing it. This method allows certain headers to be limited in the number of instances of that header that may be added to a Message programmatically. (The limit is not observed by the parser, which will faithfully produce as many headers as exist in the message being parsed.) The default implementation returns None for all header names. Nr )r r r r r �header_max_count� s zPolicy.header_max_countc C s t �dS )aZ Given a list of linesep terminated strings constituting the lines of a single header, return the (name, value) tuple that should be stored in the model. The input lines should retain their terminating linesep characters. The lines passed in by the email package may contain surrogateescaped binary data. N��NotImplementedError)r � sourcelinesr r r �header_source_parse� s zPolicy.header_source_parsec C s t �dS )z�Given the header name and the value provided by the application program, return the (name, value) that should be stored in the model. NrD �r r r r r r �header_store_parse� s zPolicy.header_store_parsec C s t �dS )aw Given the header name and the value from the model, return the value to be returned to the application program that is requesting that header. The value passed in by the email package may contain surrogateescaped binary data if the lines were parsed by a BytesParser. The returned value should not contain any surrogateescaped data. NrD rH r r r �header_fetch_parse� s zPolicy.header_fetch_parsec C s t �dS )a� Given the header name and the value from the model, return a string containing linesep characters that implement the folding of the header according to the policy controls. The value passed in by the email package may contain surrogateescaped binary data if the lines were parsed by a BytesParser. The returned value should not contain any surrogateescaped data. NrD rH r r r �fold� s z Policy.foldc C s t �dS )a% Given the header name and the value from the model, return binary data containing linesep characters that implement the folding of the header according to the policy controls. The value passed in by the email package may contain surrogateescaped binary data. NrD rH r r r � fold_binary s zPolicy.fold_binary)r r( r) r* r= �linesep�cte_type�max_line_length� mangle_from_Zmessage_factoryrA r> rC �abc�abstractmethodrG rI rJ rK rL r r r r r p s( 0 )� metaclassc @ sL e Zd ZdZdZdd� Zdd� Zdd� Zd d � Zd d � Z d d� Z dd� Z dS )r z�+ This particular policy is the backward compatibility Policy. It replicates the behavior of the email package version 5.1. Tc C s0 t |t�s|S t|�r(tj|tj|d�S |S d S )N�r � header_name)� isinstance�strr r �Header�_charset� UNKNOWN8BITrH r r r �_sanitize_header s �zCompat32._sanitize_headerc C s> |d � dd�\}}|�d�d�|dd� � }||�d�fS )a: + The name is parsed as everything up to the ':' and returned unmodified. The value is determined by stripping leading whitespace off the remainder of the first line, joining all subsequent lines together, and stripping any trailing carriage return or linefeed characters. r �:r- z � Nz )r/ �lstripr �rstrip)r rF r r r r r rG % s z Compat32.header_source_parsec C s ||fS )z>+ The name and value are returned unmodified. r rH r r r rI 1 s zCompat32.header_store_parsec C s | � ||�S )z�+ If the value contains binary data, it is converted into a Header object using the unknown-8bit charset. Otherwise it is returned unmodified. )r[ rH r r r rJ 7 s zCompat32.header_fetch_parsec C s | j ||dd�S )a + Headers are folded using the Header folding algorithm, which preserves existing line breaks in the value, and wraps each resulting line to the max_line_length. Non-ASCII binary data are CTE encoded using the unknown-8bit charset. T��sanitize)�_foldrH r r r rK > s z Compat32.foldc C s" | j ||| jdkd�}|�dd�S )a� + Headers are folded using the Header folding algorithm, which preserves existing line breaks in the value, and wraps each resulting line to the max_line_length. If cte_type is 7bit, non-ascii binary data is CTE encoded using the unknown-8bit charset. Otherwise the original source header is used, with its existing line breaks and/or binary data. Z7bitr` �ascii�surrogateescape)rb rN �encode)r r r Zfoldedr r r rL H s zCompat32.fold_binaryc C s� g }|� d| � t|t�r\t|�rL|r<tj|tj|d�}qZ|� |� d }q`tj||d�}n|}|d k r�d}| jd k r|| j}|� |j | j |d�� |� | j � d� |�S )Nz%s: rT )rU r )rM � maxlinelenr] ) rB rV rW r r rX rY rZ rO re rM r )r r r ra �parts�hrf r r r rb T s( � zCompat32._foldN) r r( r) r* rP r[ rG rI rJ rK rL rb r r r r r s )r* rQ Zemailr r rY Z email.utilsr �__all__r r1 r; �ABCMetar r r r r r r �<module> s �L f