➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yves@zioup.com
Recipients yves@zioup.com
Date 2011-02-09.02:09:59
SpamBayes Score 0.010171629
Marked as misclassified No
Message-id <1297217400.48.0.931931004137.issue11156@psf.upfronthosting.co.za>
In-reply-to
Content 
email.encoders.encode_base64 returns a str of a single long line instead of breaking it up into 76 chars line as per RFC 2045, and as implemented by email.base64mime.

Solution:
In /usr/lib/python3.1/email/encoders.py, use encodebytes instead of b64encode:

--- encoders.py 2011-02-08 09:37:21.025030051 -0700
+++ encoders.py.yves    2011-02-08 09:38:04.945608365 -0700
@@ -12,7 +12,7 @@
     ]
 
 
-from base64 import b64encode as _bencode
+from base64 import encodebytes as _bencode
 from quopri import encodestring as _encode
History
Date User Action Args
2011-02-09 02:10:00yves@zioup.comsetrecipients: + yves@zioup.com
2011-02-09 02:10:00yves@zioup.comsetmessageid: <1297217400.48.0.931931004137.issue11156@psf.upfronthosting.co.za>
2011-02-09 02:09:59yves@zioup.comlinkissue11156 messages
2011-02-09 02:09:59yves@zioup.comcreate