Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2026-05-30 06:10:49 +00:00
Code Issues Projects Releases Packages Wiki Activity

Add some clarifications about the mapping interface presented by

Browse source 
rfc822.Message objects, based on comments from Barry.
This commit is contained in:
Fred Drake 2001-05-22 14:36:30 +00:00
parent b45032e629
commit 706314909b
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Doc/lib/librfc822.tex
View file

@ -211,13 +211,15 @@ there is no header matching \var{name}, or it is unparsable, return
\code{None}.
\end{methoddesc}
\class{Message} instances also support a read-only mapping interface.
\class{Message} instances also support a limited mapping interface.
In particular: \code{\var{m}[name]} is like
\code{\var{m}.getheader(name)} but raises \exception{KeyError} if
there is no matching header; and \code{len(\var{m})},
\code{\var{m}.has_key(name)}, \code{\var{m}.keys()},
\code{\var{m}.values()} and \code{\var{m}.items()} act as expected
(and consistently).
(and consistently). \class{Message} instances also support the
mapping writable interface \code{\var{m}[name] = value} and \code{del
\var{m}[name]}.
Finally, \class{Message} instances have two public instance variables: