//usr/lib64/lib64//lib64/python2.7//ó
ÚœSec @ s6 d Z d d d g Z d d l Z d d l Z d d l Z d d l Z d d l m Z d d l m
Z
d Z d Z d
Z
d d Z d Z d
Z e
d ƒ Z e
d ƒ Z e j d e j e j Be j Bƒ Z e j d ƒ Z e j d ƒ Z e j j Z d „ Z e e d d „ Z d f d „ ƒ YZ d „ Z d „ Z! d S( s+ Header encoding and decoding functionality.t Headert
decode_headert make_headeriÿÿÿÿN( t HeaderParseError( t Charsets
t u i u iL s us-asciis utf-8s§
=\? # literal =?
(?P[^?]*?) # non-greedy up to the next ? is the charset
\? # literal ?
(?P[qb]) # either a "q" or a "b", case insensitive
\? # literal ?
(?P.*?) # non-greedy up to the next ?= is the encoded string
\?= # literal ?=
(?=[ \t]|$) # whitespace or the end of the string
s [\041-\176]+:$s
\n[^ \t]+:c C sG t | ƒ } t j | ƒ s( | d f g Sg } d } x | j ƒ D]þ} t j | ƒ so | j | d f ƒ qA n t j | ƒ } x¾| r>| j d ƒ j ƒ } | rõ | rß | d d d k rß | d d t | d f | d Append a string to the MIME header.
Optional charset, if given, should be a Charset instance or the name
of a character set (which will be converted to a Charset instance). A
value of None (the default) means that the charset given in the
constructor is used.
s may be a byte string or a Unicode string. If it is a byte string
(i.e. isinstance(s, str) is true), then charset is the encoding of
that byte string, and a UnicodeError will be raised if the string
cannot be decoded with that charset. If s is a Unicode string, then
charset is a hint specifying the character set of the characters in
the string. In this case, when producing an RFC 2822 compliant header
using RFC 2047 rules, the Unicode string will be encoded using the
following charsets in order: us-ascii, the charset hint, utf-8. The
first character set not to provoke a UnicodeError is used.
Optional `errors' is passed as the third argument to any unicode() or
ustr.encode() call.
t 8bits us-asciiN( R R/ R* R R t input_codecR> t output_codecR; R. t UTF8t UnicodeErrorR3 R ( R7 R" R# R8 t incodect ustrt outcodec( ( s$ /usr/lib64/python2.7/email/header.pyR é s(
c C s0 | j | ƒ } | j | t ƒ } | j | ƒ } | | k rI | | f g S| d k rb | | f g S| d k r„ | j | | | | ƒ S| t | ƒ k rË | } | j | | t ƒ } | j | | t ƒ }
n t | | | ƒ \ } }
| j | ƒ } | j | t ƒ } | | f g }
|
| j |
| | j | ƒ S( NRH s us-ascii(
t
to_splittablet from_splittablet Truet encoded_header_lent _split_asciiR t Falset _binsplitt _splitR6 ( R7 R" R# R' t
splitcharst
splittableR% t elent splitpntt firstt lastt fsplittablet fencodedt chunk( ( s$ /usr/lib64/python2.7/email/header.pyRW s$
c C s8 t | | | j | j | ƒ } t | | g t | ƒ ƒ S( N( RT R6 R0 t zipR ( R7 R" R# t firstlenRX t chunks( ( s$ /usr/lib64/python2.7/email/header.pyRT N s c C s± g } xŽ | D]† \ } } | s% q
n | d k s@ | j d k rI | } n | j | ƒ } | rz | d j d ƒ rz d } n d } t | | | | ƒ q
Wt | j } | j | ƒ S( NiÿÿÿÿR R ( R t header_encodingt
header_encodet endswitht _max_appendt NLR0 R@ ( R7 t newchunksR' Rc R R# R" t extrat joiner( ( s$ /usr/lib64/python2.7/email/header.pyt _encode_chunksS s
s ;, c C sÓ g } | j } d } x~ | j D]s \ } } | | d } | | j d ƒ k rW | } n | | j | | | | ƒ 7} | d \ } } | j | ƒ } q W| j | | ƒ }
t j |
ƒ rÏ t d j |
ƒ ƒ ‚ n |
S( s‡ Encode a message header into an RFC-compliant format.
There are many issues involved in converting a given string for use in
an email header. Only certain character sets are readable in most
email clients, and as header strings can only contain a subset of
7-bit ASCII, care must be taken to properly convert and encode (with
Base64 or quoted-printable) header strings. In addition, there is a
75-character length limit on any given encoded header field, so
line-wrapping must be performed, even with double-byte character sets.
This method will do its best to convert the string to the correct
character set used in email, and encode and line wrap it safely with
the appropriate scheme for that character set.
If the given charset is not known or an error occurs during
conversion, this function will return the header untouched.
Optional splitchars is a string containing characters to split long
ASCII lines on, in rough support of RFC 2822's `highest level
syntactic breaks'. This doesn't affect RFC 2047 encoded lines.
i i R iÿÿÿÿs8 header value appears to contain an embedded header: {!r}( R5 R3 RS RW Rl t _embeded_headerR R t format( R7 RX Ri R' t lastlenR" R# t targetlent lastchunkt lastcharsett value( ( s$ /usr/lib64/python2.7/email/header.pyR; v s N(
t __name__t
__module__R R: R< RD RF RG R RW RT Rl R; ( ( ( s$ /usr/lib64/python2.7/email/header.pyR s 3 7 . #c C s| g } | } xi| j ƒ D][} | j ƒ } t | ƒ | k rV | j | ƒ | } q n x4 | D] } | | k r] Pq] q] W| j | ƒ | } q t j d | ƒ } | d k rµ | }
n d }
|
d } t | ƒ } t | j d t ƒ ƒ }
g } d } x]| j | ƒ D]L} | t d t | ƒ d ƒ | } t | ƒ } | } | d k r| rt | ƒ d k rt
j | d ƒ r| j | ƒ | | 7} q| | | k r:| rÃ| j | j | ƒ |
ƒ n | | k r| d k rt
| | | | d ƒ } | j | d ƒ | d g } n | g } |
t | d ƒ } | } q| j | ƒ | | 7} qW| r | j | j | ƒ ƒ q q W| S( Ns %s\s*s ;,R R s i i iÿÿÿÿ( R
t lstripR R t ret compileR1 R2 R t maxt fcret matchR@ RT t extend( R" Rb t restlenR) RX t linest maxlenR t cht cret eolRk t joinlent wslent thist linelent partt curlent partlent onfirstlinet subl( ( s$ /usr/lib64/python2.7/email/header.pyRT ¢ s^
! %
c
C s± d } t | ƒ } xf | | k rz | | d d ?} | j | | t ƒ } | j | ƒ } | | k rm | } q | d } q W| j | | t ƒ } | j | | t ƒ } | | f S( Ni i ( R RQ RR RS RU (
RY R# R' t it jt mR` t chunklenR\ R] ( ( s$ /usr/lib64/python2.7/email/header.pyRV è s (" t __doc__t __all__Rw R t email.quoprimimeR t email.base64mimet email.errorsR t
email.charsetR Rh R R= R2 R? R4 R. RK Rx t VERBOSEt
IGNORECASEt MULTILINER
Rz Rm R Rg R R R R RT RV ( ( ( s$ /usr/lib64/python2.7/email/header.pyt s:
< ÿ F