[Python-Dev] PEP 385: the eol-type issue

M.-A. Lemburg mal at egenix.com
Fri Aug 7 14:48:39 CEST 2009

Antoine Pitrou wrote:
> M.-A. Lemburg <mal <at> egenix.com> writes:
>> IMHO, it would be a lot better to add full Unicode support
>> for line breaks to the io layer. Given that the code for the
>> complicated handling of the CRLF combination is already there,
>> it's not difficult to add support for the remaining line break
>> characters.
> I'm not against anything in principle here, but I'd just like to point out two
> things:
> 1. Changing line break semantics would break compatibility with the current
> behaviour, and it would also diverge from what the `newline` parameter
> specifies; this may be annoying if, for example, the TextIOWrapper class is used
> to parse some network protocols with a rigorous line ending definition

Sure, but that would still be possible using the newline parameter.
We'd only have to find a way to tell the io layer "accept all Unicode
line break characters".

> 2. It would be useful to have some input by the original designers of the IO
> library (the PEP lists Guido, Daniel Stutzbach and Mike Verdone, but I suppose
> other people were involved)

Fair enough.

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Aug 07 2009)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the Python-Dev mailing list