Still same bug even with email ver. 1.2

[Michael Hudson]

woodsplitter at rocketmail.com (David Rushby) writes:

> And here's SourceForge bug #491612 (closed now), which was filed to
> report this very bug:
> http://sourceforge.net/tracker/index.php?func=detail&aid=491612&group_id=25568&atid=384678
> 
> Unfortunately, contrary to Oleg's assertion in c.l.py and Barry's in
> his message added to the SF bug report, the CVS version of has *not*
> been fixed.

Are you sure?  It's certainly possible, but I think revision 1.6 of
Lib/email/Parser.py, which became revision 1.5.10.1 on the
release22-maint branch, was certainly aimed at fixing this bug.

> The bug is a showstopper for the email package (it stopped my show,
> at least), but the fix is quite simple.  Could we get it fixed
> before the final release of Python 2.2.1?

If it's not already, probably.  2.2.1c1 is imminent (later today, I
hope) and it's too late to change that.

> Should someone resubmit the bug to mimelib's SourceForge bug tracker,
> or will this message be enough?

First it would be good if you could supply some evidence that the bug
isn't, in fact, fixed.

Cheers,
M.

-- 
  [Perl] combines all the worst aspects of C and Lisp: a billion
  different sublanguages in one monolithic executable.  It combines
  the power of C with the readability of PostScript. -- Jamie Zawinski