Hacked By AnonymousFox
B
�A�[�P � @ s� d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddl
mZ dd l
mZ dd
l
m
Z G dd� de�ZG d
d� de�ZG dd� de�Zdd� ZG dd� de�ZG dd� de�ZG dd� de�ZG dd� de�ZG dd� de�ZG dd� de�ZG dd � d e�ZG d!d"� d"e�ZG d#d$� d$e�ZG d%d&� d&e�ZG d'd(� d(e�ZG d)d*� d*e�ZG d+d,� d,e�Z eeeeeeeeeeeeeeeeeee d-�Z!G d.d/� d/e�Z"d0S )1a; Representing and manipulating email headers via custom objects.
This module provides an implementation of the HeaderRegistry API.
The implementation is designed to flexibly follow RFC5322 rules.
Eventually HeaderRegistry will be a public API, but it isn't yet,
and will probably change some before that happens.
� )�unicode_literals)�division)�absolute_import)�super)�str)�text_to_native_str)�utils)�errors)�_header_value_parserc @ s^ e Zd Zddd�Zedd� �Zedd� �Zed d
� �Zedd� �Zd
d� Z dd� Z
dd� ZdS )�Address� Nc C sl |dk rV|s|rt d��t�|�\}}|r:td�||���|jrJ|jd �|j}|j}|| _|| _ || _
dS )a� Create an object represeting a full email address.
An address can have a 'display_name', a 'username', and a 'domain'. In
addition to specifying the username and domain separately, they may be
specified together by using the addr_spec keyword *instead of* the
username and domain keywords. If an addr_spec string is specified it
must be properly quoted according to RFC 5322 rules; an error will be
raised if it is not.
An Address object has display_name, username, domain, and addr_spec
attributes, all of which are read-only. The addr_spec and the string
value of the object are both quoted according to RFC5322 rules, but
without any Content Transfer Encoding.
Nz=addrspec specified when username and/or domain also specifiedz6Invalid addr_spec; only '{}' could be parsed from '{}'r )� TypeError�parserZ
get_addr_spec�
ValueError�format�all_defects�
local_part�domain�
_display_name� _username�_domain)�self�display_name�usernamer � addr_specZa_s�rest� r �V/opt/alt/python37/lib/python3.7/site-packages/future/backports/email/headerregistry.py�__init__ s
zAddress.__init__c C s | j S )N)r )r r r r r <