W
W. eWatson
I wrote a Python program that creates a folder with a file in it.
Unfortunately, I did not close the file. Further, the file was empty.
When I tried to delete via XP menu for the file, XP objected on the
grounds the file was being used somewhere else.
I suspect that some process was using within Python to execute the
program was alive and still had a grip on the file.
I did manage to delete the derelict file once. It was after I had
rebooted.
How does ibe generally get out of this? I've had this sort of thing
happen before when I was trying to rename a file, and XP objected for
the reason above. If I continued with other matters, I've found I could
return and delete it.
Unfortunately, I did not close the file. Further, the file was empty.
When I tried to delete via XP menu for the file, XP objected on the
grounds the file was being used somewhere else.
I suspect that some process was using within Python to execute the
program was alive and still had a grip on the file.
I did manage to delete the derelict file once. It was after I had
rebooted.
How does ibe generally get out of this? I've had this sort of thing
happen before when I was trying to rename a file, and XP objected for
the reason above. If I continued with other matters, I've found I could
return and delete it.