[Python-3000] [Python-Dev] Universal newlines support in Python 3.0
barry at python.org
Wed Aug 15 06:33:46 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
On Aug 15, 2007, at 12:03 AM, Guido van Rossum wrote:
> On 8/14/07, Barry Warsaw <barry at python.org> wrote:
>> On Aug 14, 2007, at 12:52 PM, Guido van Rossum wrote:
>>> On 8/14/07, Barry Warsaw <barry at python.org> wrote:
>>>> It would have been perfect, I think, if I could have opened the
>>>> in text mode so that read() gave me strings, with universal
>>>> and preservation of line endings (i.e. no translation to \n).
>>> You can do that already, by passing newline="\n" to the open()
>>> function when using text mode.
>> Cute, but obscure. I'm not sure I like it as the ultimate way of
>> spelling these semantics.
> It was the best we could come up with in the 3 minutes we devoted to
> this at PyCon when drafting PEP 3116. If you have a better idea,
> please don't hide it!
I think you (almost) suggested it in your first message! Add a flag
called preserve_eols that defaults to False, is ignored unless
universal newline mode is turned on, and when True, disables the
replacement on input.
>> There's still a problem though: this works for .readlines() but not
>> for .read() which unconditionally converts \r\n to \n. The
>> FeedParser uses .read() and I think the behavior should be the same
>> for both methods.
> Ow, that's a bug! I'll look into fixing it; this was unintentional!
Oh, excellent! I think that will nicely take care of email package's
needs and will allow me to remove the crufty conversion.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
More information about the Python-3000