On 12/08/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Note that Python does nothing special in the above case. For non-Windows
> platforms, you'd get two different results -- the conversion from \r\n to
> \n is done by the Windows C runtime since the default open() mode is text
> mode.
>
> Only w
Paul Moore schrieb:
> Specifically, I'm looking to replicate this behaviour:
>
>>xxd crlf
> 000: 610d 0a62 0d0a a..b..
>
>>xxd lf
> 000: 610a 620aa.b.
>
>>python
> Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 b
On 11/08/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/11/07, Tony Lownds <[EMAIL PROTECTED]> wrote:
> > Is this ok: when newline='\r\n' or newline='\r' is passed, only that
> > string is used to determine
> > the end of lines. No translation to '\n' is done.
>
> I *think* it would be more
I'd like to remove support for Windows 9x (95, 98(SE), ME)
soon from the Python trunk. This would primarily affect all
wide-string APIs (which would be considered present
unconditionally), as well as certain "new" Win32 functions;
in this cleanup, I would also drop support for NT+ before
Windows 20
