René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support multiline output in binascii.b2a_base64() and base64.b64encode()","articleBody":"# Feature or enhancement\n\nAccording to [RFC 4648, section 3.1](https://datatracker.ietf.org/doc/html/rfc4648#section-3.1):\n\n    Implementations MUST NOT add line feeds to base-encoded data unless\n    the specification referring to this document explicitly directs base\n    encoders to add line feeds after a specific number of characters.\n\nBut many specifications use Base 64 separated on lines of fixed length. The stdlib code contains multiple functions that take the Base 64 data and split it on multiple lines. It is worth to add a special support of this in the base functions that encode to Base 64 -- to improve maintenability (there is a known bug in `email.base64mime.body_encode()`), convenience and performance.\n\nI choose name `wrapcol` for the parameter because it is already used in `base64.a85encode()`. Other (mostly private) functions that implement the Base 64 wrapping use different names: `maxlinelen`, `maxlen`, `max_line_length`. PR #102753 propose name `width` for `binascii.b2a_ascii85()` (it is also used in `textwrap`). So there is no consistency or single dominant option, but I am open for suggestions.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-143216\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/serhiy-storchaka","@type":"Person","name":"serhiy-storchaka"},"datePublished":"2025-12-27T11:47:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/143214/cpython/issues/143214"}