kxroberto kxrobe...@users.sourceforge.net added the comment:
I'd still say this is a plain bug, which simply should be fixed.
People who have working code must have already a smart work around: either -
or! : By doing the 5 low level code lines of .as_string() on their own. (there
is no other
R. David Murray rdmur...@bitdance.com added the comment:
On balance I think this would be a backward incompatible change that has
insufficient benefit to be worth doing. People who have working code will be
depending on the existing defaults of the two methods, and changing this out
from
Changes by Barry A. Warsaw ba...@python.org:
--
assignee: barry - r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1459867
___
___
R. David Murray rdmur...@bitdance.com added the comment:
If I understand correctly, this is related to issue 1440472. There the
complaint is made that what you get out is not what you put in, since unixfrom
defaults to True. But that's only true for __str__. As kxroberto points out,
in
kxroberto kxrobe...@users.sourceforge.net added the comment:
g = Generator(fp,mangle_from_=unixfrom)
in that code location below?
It produced exceptions often when message lines (or headerlines e.g.
Subject also when I remember right) begin with the char or so.
--- Message.py.orig
