Closed nsheff closed 4 years ago
It looks like it's a known quirk of shutil.rmtree
https://stackoverflow.com/questions/1557351/python-delete-non-empty-dir/21966211#21966211
turns out -- the problem was that there were still some files in there that were being accessed by a process. so, typically, this wouldn't come up... but if there's some zombie or something still touching a file then they can't be removed, and it leads to errors. so, not really looper's fault...
Got this error running
looper destroy
: