-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 13, 2007, at 2:43 PM, Bill Janssen wrote:
I see that base64.b64encode and base64.standard_b64encode no longer
introduce line breaks into the output strings, as base64.encodestring
does. Shouldn't there be an option on one of them to do
I see that base64.b64encode and base64.standard_b64encode no longer
introduce line breaks into the output strings, as base64.encodestring
does. Shouldn't there be an option on one of them to do this?
See:
http://mail.python.org/pipermail/python-bugs-list/2001-October/
007856.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 14, 2007, at 3:20 PM, Bill Janssen wrote:
I think that's probably right. I just added the PEM line-wrapping to
the code in the ssl module. Though I hate to keep adding
line-wrapping code here and there... Perhaps just adding a utility
Does anything in textwrap already do the trick? If not, that might
be the best place to refactor similar code to.
Yes, textwrap.fill. Thanks for pointing it out.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 14, 2007, at 6:01 PM, Bill Janssen wrote:
Does anything in textwrap already do the trick? If not, that might
be the best place to refactor similar code to.
Yes, textwrap.fill. Thanks for pointing it out.
/me tries to remember that for
I see that base64.b64encode and base64.standard_b64encode no longer
introduce line breaks into the output strings, as base64.encodestring
does. Shouldn't there be an option on one of them to do this?
Bill
___
Python-Dev mailing list
I see that base64.b64encode and base64.standard_b64encode no longer
introduce line breaks into the output strings, as base64.encodestring
does. Shouldn't there be an option on one of them to do this?
See:
http://mail.python.org/pipermail/python-bugs-list/2001-October/007856.html
section 2.1
