Timeline for Unable to delete .lock files within geodatabase using Python
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 2, 2016 at 22:51 | answer | added | crld | timeline score: 1 | |
Dec 3, 2015 at 22:32 | comment | added | jpmc26 |
For the record, this is probably a good thing. .lock files generally indicate that something is in use. You don't want to delete something in use by an application. You want to stop using it first. (I consider it a weakness of the GDB format that you could go delete other files that belong to it while this one is locked.) Also, don't use distutils for file management; that's for creating distribution packages for Python code.
|
|
Dec 20, 2013 at 17:43 | answer | added | Adio3012 | timeline score: 0 | |
Jun 2, 2013 at 7:58 | history | edited | PolyGeo♦ |
edited tags
|
|
Oct 8, 2012 at 16:34 | comment | added | blah238 | Also if you have the geodatabase open in ArcMap, ArcCatalog, etc., you will not be able to delete it except within the application that has the lock on it. | |
Oct 8, 2012 at 16:32 | comment | added | blah238 |
Have you considered using arcpy.Copy_management and arcpy.Delete_management to do this?
|
|
Oct 8, 2012 at 15:52 | history | edited | Matt | CC BY-SA 3.0 |
added 25 characters in body; edited title
|
Oct 8, 2012 at 15:47 | history | asked | Matt | CC BY-SA 3.0 |