*jR D S r SSKJr SSKJr SSKJr SSKJr " S S5 r " S S 5 r " S S\ 5 rS r " S S5 r " S S\ 5 r " S S5 r " S S\5 r " S S5 r " S S\5 r " S S\5 r " S S\5 r " S S5 r " S S 5 r " S! S"\5 r " S# S$\5 r " S% S&5 r " S' S(5 r " S) S*5 r0 S+\_S,\_S-\_S.\_S/\_S0\_S1\_S2\_S3\_S4\_S5\_S6\_S7\_S8\_S9\_S:\_S;\_\\\\\S<.Er " S= S>5 rg?)@zRepresenting 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. )MappingProxyType)utils)errors)_header_value_parserc p \ rS rSrSS jr\S 5 r\S 5 r\S 5 r\S 5 r S r S rS rSr g) Address Nc SR [ SXX445 5 nSU; d SU; a [ S5 eUb U( d U( a [ S5 e[ R " U5 u pgU( a [ SR Xd5 5 eUR ( a UR S eUR nUR nXl X l X0l g) a Create an object representing 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. N z8invalid arguments; address parts cannot contain CR or LFz=addrspec specified when username and/or domain also specifiedz6Invalid addr_spec; only '{}' could be parsed from '{}'r ) joinfilter ValueError TypeErrorparser get_addr_specformatall_defects local_partdomain _display_name _username_domain)selfdisplay_nameusernamer addr_specinputsa_srests ;/opt/alt/python313/lib64/python3.13/email/headerregistry.py__init__Address.__init__ s " |v&QRS6>TV^WXX 6 !8 9 9,,Y7IC "==CV$'>45 5 ooa((~~HZZF)! c U R $ Nr r s r" r Address.display_name8 !!!r% c U R $ r' )r r) s r" r Address.username<