[New-bugs-announce] [issue5430] Must not replace LF or CR by CRLF in literals

Memeplex report at bugs.python.org
Fri Mar 6 08:51:17 CET 2009

New submission from Memeplex <carlosjosepita at gmail.com>:

For example, after that "normalization", quoted printable encoded
headers (as described at rfc 2047) longer than 76 characters are
splitted in two different ill-formed headers because the soft LF line
break becomes a "hard" CRLF one. This is clearly wrong.

rfc 2060 specifically allows CR and LF inside literals:

A literal is a sequence of zero or more octets (including CR and LF),
prefix-quoted with an octet count in the form of an open brace ("{"),
the number of octets, close brace ("}"), and CRLF.

components: Library (Lib)
messages: 83241
nosy: memeplex
severity: normal
status: open
title: Must not replace LF or CR by CRLF in literals
type: behavior
versions: Python 2.6

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list