clean up back_up_file implementation & test #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First round of cleanup for easybuilders#2134, only touching
back_up_file
for now; more to come (trying to send you bite-sized PRs)Re-ran the original test after cleaning up
back_up_file
to make sure behaviour remains the same, then also cleaned up test.One thing that came to mind is that it's maybe better to back up files with a more meaningful filename like
test.txt_201708170828
, i.e. date + timestamp as increasing number, and on a clash, we can simply sleep for 1 sec and try again?