Message250520
| Author | martin.panter |
|---|---|
| Recipients | BreamoreBoy, aleperalta, barry, berker.peksag, brett.cannon, docs@python, jcea, martin.panter, ncoghlan, python-dev, r.david.murray, serhiy.storchaka |
| Date | 2015-09-12.12:16:03 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1442060164.44.0.759167319037.issue16473@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The list of functions were added in Issue 17844. I made the change today because I forgot that the listed functions weren’t exactly equivalent when investigating Issue 25075. Base64-codec encodes to multiple lines, but b64encode() returns the raw encoding without line breaks. I see that base64.encodebytes() is listed as a “legacy interface”, but as far as I can tell nothing outside the legacy interface does any line splitting. Hex-codec encodes to lowercase, but b16encode() returns uppercase, following RFC 4648. Quopri-codec encodes all whitespace, but quopri.encodestring() lets most whitespace through verbatim by default. In this case I think it would be reasonable to change back to encodestring() if we say that quotetabs=True is passed in. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-09-12 12:16:04 | martin.panter | set | recipients: + martin.panter, barry, brett.cannon, jcea, ncoghlan, r.david.murray, docs@python, BreamoreBoy, python-dev, berker.peksag, serhiy.storchaka, aleperalta |
| 2015-09-12 12:16:04 | martin.panter | set | messageid: <1442060164.44.0.759167319037.issue16473@psf.upfronthosting.co.za> |
| 2015-09-12 12:16:04 | martin.panter | link | issue16473 messages |
| 2015-09-12 12:16:03 | martin.panter | create | |