Closed GoogleCodeExporter closed 9 years ago
Original comment by lobais
on 16 Nov 2007 at 6:25
In changeset 3c1e0bb029d4 I used ~/.local/share/pychess/engines/ (or
equivalent). Fixing this creates a question: how can we stop a build-up of
engine logs? If we delete all old files we risk killing learning files created
by engines, or support files put there intentionally by users. Maybe this will
be OK when we have engine config dialogs.
Original comment by Uncombed...@gmail.com
on 7 Apr 2011 at 12:54
Hm, for a start I don't think the files are gonna fill up the users hard drive.
If it becomes a problem, could we ask the OS when the files were last read? If
it's not read, it's not a learning file. Actually, if it's not written to, it's
probably isn't one either.
Original comment by lobais
on 7 Apr 2011 at 7:20
os.stat gives us all the file information we could want.
Original comment by lobais
on 7 Apr 2011 at 7:27
Original comment by gbtami
on 7 May 2013 at 12:02
Original issue reported on code.google.com by
lobais
on 6 Oct 2007 at 7:02