Dennis Lee Bieber wrote:
On Mon, 07 Jul 2008 01:03:10 -0700, norseman <[EMAIL PROTECTED]>
declaimed the following in comp.lang.python:
>
> Normal file I/O sequence:
>
> fp = open(target, 'wb')
>
> fp.seek(-1, 2)
>
> fp.write(record)
>
Except it doesn't do that in Windows. See belo
norseman wrote:
> In this case it's [MS Windows] (still) 'cooking' the writes even
> with 'rwb' and O_RDWR|O_BINARY in (proper respective) use.
>
> Specific: python created and inspected binary file ends:
> 00460: 0D 1A(this is correct)
I'm not actually sure what the 0x1a is supposed to
On Jul 7, 10:18 am, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote:
> On Mon, 07 Jul 2008 01:03:10 -0700, norseman <[EMAIL PROTECTED]>
> declaimed the following in comp.lang.python:
>
>
>
> > > Normal file I/O sequence:
>
> > > fp = open(target, 'wb')
>
> > > fp.seek(-1, 2)
>
> > > fp.write(record
I know I saw the answer recently, as in since February '08, but I can't
re-find it. :( I tried the mail archives and such and my own
collections but the piece I saw still eludes me.
Problem: (sos=same old s...) Microsoft insists the world work it's way
even when the Microsoft way was pro
norseman <[EMAIL PROTECTED]> wrote:
>
>Problem: (sos=same old s...) Microsoft insists the world work it's way
>even when the Microsoft way was proven wrong decades ago. In this case
>it's (still) 'cooking' the writes even with 'rwb' and O_RDWR|O_BINARY in
>(proper respective) use.
No, it does
norseman wrote:
I know I saw the answer recently, as in since February '08, but I can't
re-find it. :( I tried the mail archives and such and my own
collections but the piece I saw still eludes me.
Problem: (sos=same old s...) Microsoft insists the world work it's way
even when the Mi
I know I saw the answer recently, as in since February '08, but I can't
re-find it. :( I tried the mail archives and such and my own
collections but the piece I saw still eludes me.
Problem: (sos=same old s...) Microsoft insists the world work it's way
even when the Microsoft way was p
