Message102863
| Author |
tim.golden |
| Recipients |
asvetlov, brian.curtin, flox, jafo, jaraco, loewis, r.david.murray, techtonik, tim.golden |
| Date |
2010年04月11日.18:38:06 |
| SpamBayes Score |
0.00064073905 |
| Marked as misclassified |
No |
| Message-id |
<4BC216E5.7020205@timgolden.me.uk> |
| In-reply-to |
<1271008677.44.0.578850641014.issue7443@psf.upfronthosting.co.za> |
| Content |
I'm afraid that the problem doesn't lie in the unlink: DeleteFile
succeeds. The problem is that the file is only marked for delete
until such time as the last SHARE_DELETE handle on it is closed.
Until that time, an attempt to (re)create the file for anything
other than SHARE_DELETE will fail. As you say, it's a timing
issue.
Making os.unlink on Windows more robust may be a good
idea, but it's not going to help this issue. See my test-case.py
on an earlier message for reproduction:
http://bugs.python.org/file16869
TJG |
|