Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Applied 2nd solution as r61951
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1561
__
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Three months later, one obvious correction: open all (text) files with
the newline='\n' option.
- This makes files identical between Unix and Windows version
- no more os.linesep
A compatibility problem: mailboxes created with python2.6
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Another patch, which uses newline='' instead. Tests pass.
The patch is much smaller, and old files are more likely to be compatible.
OTOH, messages are unicode strings with \r\n.
Which one do you prefer?
Added file:
Changes by Christian Heimes:
--
nosy: +tiran
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1561
__
___
Python-bugs-list mailing list
Unsubscribe:
Paul Moore added the comment:
I believe that mailbox.py is expected to work with files opened in
binary mode. A long time ago I opened a bug on th email package
(http://bugs.python.org/issue586899) which turned out to be because
mailbox.py required binary mode files. The conclusion was that it
Amaury Forgeot d'Arc added the comment:
mailbox.py is expected to work with files opened in binary mode
Not everywhere, unfortunately. Some files are still opened in text mode.
And this makes a huge difference with py3k: one accepts bytes, the other
requires strings.
