Closed verybadsoldier closed 6 years ago
As a nice to have, the file could have its modification timestamp set correctly, but I think it's fine (unless someone needs it).
Added that in the latest commit. Good point.
My only concern would be whether the file names should really be stored using absolute paths. I had some troubles opening them under Windows (see the double backslash in the path).
Well, I am not entirely happy with it either but I had no good alternative idea yet. One obvious option would be to store all files as a flat structure in the ZIP. Duplicated filenames would have to been handled. Probably like myfile.py
and myfile.py (2)
.
But preserving the original directory structure of the files would generally be nice also.
1) regarding Python 3.5: I am not sure how long Sacredboard should support it. I am quite happy that there not (that many) people reporting incompatibility with Python 2.7. Maybe it's also time to abandon 3.5 compatibility. I don't have enough data to decide :(
2) regarding paths: It's fine for me with absolute paths but an alternative might be using the experiment's base_dir
. But I'm not sure what happens if one of the files were stored outside that base dir. I think we are better off with absolute paths than to mess with such special cases.
I will try to work around that failing test_removing_a_run*
tests. Something in the testing library must have changed.
I am currently struggling to get the high score on those Travis checks ;-)
I have marked the failing tests to be skipped because the problem is obviously not in Sacredboard.
Adds viewing and downloading source and artifact files.
Solves #81 and #91