|
Size: 633
Comment: under construction
|
Size: 1595
Comment: follow title update for issue2524
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| Normally, Python's '`os.unlink(f)`' deletes the file f. | This page describes what happens when Python's '`os.unlink(f)`' is called on Windows. |
| Line 9: | Line 9: |
| On Windows, if f has been opened for reading by another process with '`posixfile(f)`', calling | == File opened using Python's "open" == If the file f itself or ''any hardlinked copy of f'' has been opened for reading by another process using Python's '`open()`', then '`os.unlink(f)`' will raise {{{ WindowsError: [Error 32] The process cannot access the file because it is being used by another process: <f> }}} == File opened using Mercurial's "posixfile" == If the file f has been opened for reading by another process with '`posixfile(f)`', calling |
| Line 14: | 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`' |
.(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`' .(d) calling '`os.lstat(f)`' will raise '`WindowsError: [Error 5] Access is denied: <f>`' .(e) calling '`os.path.exists(f)`' returns False |
| Line 19: | Line 34: |
| == See also == * Bts:issue2524: "update loses working copy files on Windows for open files" * Bts:issue2543: "os.unlink deletes wrong file on windows share served by Samba" * [[http://mercurial.markmail.org/thread/t5ecar6sn3ekifo6|How Mercurial could be made working with Virus Scanners on Windows]] |
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 itself or any hardlinked copy of f has been opened for reading by another process using Python's 'open()', 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'
(d) calling 'os.lstat(f)' will raise 'WindowsError: [Error 5] Access is denied: <f>'
(e) calling 'os.path.exists(f)' returns False
Scheduled delete is left as soon as the other process closes the file.
3. See also
issue2524: "update loses working copy files on Windows for open files"
issue2543: "os.unlink deletes wrong file on windows share served by Samba"
How Mercurial could be made working with Virus Scanners on Windows