Differences between revisions 3 and 4
Revision 3 as of 2010-11-29 10:31:31
Size: 1005
Editor: abuehl
Comment:
Revision 4 as of 2010-11-29 22:29:08
Size: 1102
Editor: abuehl
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
 (c) calling '`os.rename(f, f+'.foo')`' will raise '`WindowsError: [Error 5] Access is denied`'

Unlinking Files on Windows

/!\ This page is intended for developers.

This page describes what happens when Python's 'os.unlink(f)' is called on Windows.

1. File opened using Python's "open"

If the file f has been opened for reading by another process using Python's 'open(f)', then 'os.unlink(f)' will raise

WindowsError: [Error 32] The process cannot access the file because it is being
used by another process: <f>

2. File opened using Mercurial's "posixfile"

If the file f has been opened for reading by another process with 'posixfile(f)', calling unlink will send that file into a "scheduled delete" state.

Scheduled delete has the following characteristics:

  • (a) the entry in the directory for f is still kept

    (b) calling 'fd = posixfile(f, 'w')' will raise 'IOError: [Errno 13] <f>: Access is denied' (c) calling 'os.rename(f, f+'.foo')' will raise 'WindowsError: [Error 5] Access is denied'

Scheduled delete is left as soon as the other process closes the file.


CategoryInternals

UnlinkingFilesOnWindows (last edited 2017-09-02 08:00:32 by abuehl)