mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-11 14:44:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Added a note about the somewhat kludgey behavior of the message

Browse source 
epilogue, based on the discussion in this SF bug report:

https://sourceforge.net/tracker/index.php?func=detail&aid=472481&group_id=25568&atid=384678
This commit is contained in:
Barry Warsaw 2001-10-19 04:34:42 +00:00
parent 1f0fa92b0a
commit e736d93eab
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Doc/lib/emailmessage.tex
View file

@ -390,4 +390,14 @@ Note that if the message object has no preamble, the
The \var{epilogue} attribute acts the same way as the \var{preamble} The \var{epilogue} attribute acts the same way as the \var{preamble}
attribute, except that it contains text that appears between the last attribute, except that it contains text that appears between the last
boundary and the end of the message. boundary and the end of the message.
One note: when generating the flat text for a \mimetype{multipart}
message that has no \var{epilogue} (using the standard
\class{Generator} class), no newline is added after the closing
boundary line. If the message object has an \var{epilogue} and its
value does not start with a newline, a newline is printed after the
closing boundary. This seems a little clumsy, but it makes the most
practical sense. The upshot is that if you want to ensure that a
newline get printed after your closing \mimetype{multipart} boundary,
set the \var{epilogue} to the empty string.
\end{datadesc} \end{datadesc}