From cfe4df170c3ec0af1d006960afac621849115225 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Tue, 22 May 2001 15:17:12 +0000 Subject: Add a list of mapping interface methods which are not supported by rfc822.Message (per Barry's comments). --- Doc/lib/librfc822.tex | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Doc/lib/librfc822.tex b/Doc/lib/librfc822.tex index 56f6c74..87e1619 100644 --- a/Doc/lib/librfc822.tex +++ b/Doc/lib/librfc822.tex @@ -219,7 +219,10 @@ there is no matching header; and \code{len(\var{m})}, \code{\var{m}.values()} and \code{\var{m}.items()} act as expected (and consistently). \class{Message} instances also support the mapping writable interface \code{\var{m}[name] = value} and \code{del -\var{m}[name]}. +\var{m}[name]}. \class{Message} objects do not support the +\method{clear()}, \method{copy()}, \method{get()}, \method{popitem()}, +\method{setdefault()}, or \method{update()} methods of the mapping +interface. Finally, \class{Message} instances have two public instance variables: -- cgit v0.12