|
Size: 1102
Comment:
|
Size: 1103
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 26: | Line 26: |
| (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`' |
.(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`' |
| Line 32: | Line 32: |
Unlinking Files on Windows
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
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.