[Python-checkins] python/dist/src/Doc/lib emailparser.tex, 1.8.16.1, 1.8.16.2

[bwarsaw at users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2492

Modified Files:
      Tag: release23-maint
	emailparser.tex 
Log Message:
Fix for SF bug # 1032960.


Index: emailparser.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/emailparser.tex,v
retrieving revision 1.8.16.1
retrieving revision 1.8.16.2
diff -u -d -r1.8.16.1 -r1.8.16.2
--- emailparser.tex	24 Feb 2004 20:57:30 -0000	1.8.16.1
+++ emailparser.tex	9 Oct 2004 21:33:24 -0000	1.8.16.2
@@ -50,12 +50,13 @@
 arguments.
 
 The optional \var{strict} flag specifies whether strict or lax parsing
-should be performed.  Normally, when things like MIME terminating
+should be performed.  When things like MIME terminating
 boundaries are missing, or when messages contain other formatting
 problems, the \class{Parser} will raise a
-\exception{MessageParseError}.  However, when lax parsing is enabled,
-the \class{Parser} will attempt to work around such broken formatting
-to produce a usable message structure (this doesn't mean
+\exception{MessageParseError}, if the \var{strict} flag is \code{True}.
+However, when lax parsing is enabled (i.e. \var{strict} is \code{False}),
+the \class{Parser} will attempt to work around such broken formatting to
+produce a usable message structure (this doesn't mean
 \exception{MessageParseError}s are never raised; some ill-formatted
 messages just can't be parsed).  The \var{strict} flag defaults to
 \code{False} since lax parsing usually provides the most convenient