467,925 Members | 2,002 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,925 developers. It's quick & easy.

Re: How to bypass Windows 'cooking' the I/O? (One more time, please)II

On Jul 7, 10:18*am, Dennis Lee Bieber <wlfr...@ix.netcom.comwrote:
On Mon, 07 Jul 2008 01:03:10 -0700, norseman <norse...@hughes.net>
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 below.

* * * * I wouldn't expect that sequence to work on any system... The "w"
implies "create new file, or truncate existing file to 0-bytes, then
write data to it" -- with no seeking permitted. You must include the "+"
to do seeking, and if you want to retain the existing file contents you
probably need to open with "a+" ("a" for append).

* * * * The rest of your situation I won't touch. Other than to wonder why
the situation hasn't hit any of the various database servers which must
be operating in binary mode, and perform lots of seeking... Surely
somewhere out someone else must have encountered a seek crossing an
apparent <cr><eofmark (which isn't a normal Windows sequence anyway --
since Windows uses <cr><lffor EOL, I'd have expected to see a problem
if backing over a <cr><lf><eof>)
--
* * * * Wulfraed * * * *Dennis Lee Bieber * * * ** * * KD6MOG
* * * * wlfr...@ix.netcom.com * * * * * * *wulfr...@bestiaria.com
* * * * * * * * HTTP://wlfraed.home.netcom.com/
* * * * (Bestiaria Support Staff: * * * * * * * web-a...@bestiaria.com)
* * * * * * * * HTTP://www.bestiaria.com/

lol @ op not finding the answer to his question in the archives, then
being answered again by someone who doesn't let his answer go in the
archive. How useful.
Jul 7 '08 #1
  • viewed: 675
Share:

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Colin Brown | last post: by
13 posts views Thread by BigDaDDY | last post: by
3 posts views Thread by luscus | last post: by
12 posts views Thread by Joey Powell | last post: by
4 posts views Thread by Edwin G. Castro | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.