Robustness of copy command

[dsmeister]

Hi

Edit: It seems I was a bit early, apparently in this configuration it only copied a blank document. I have it working in the original version albeit with the error message now, thank you for your great work. If you ever find out what the problem is I'd love to know.

Love what you did. I got a few error messages specifically when working on windows and using the connector for fusion app(in order to sync thread data with the whole team). After some trial and error and a little help from our friendly neighbourhood AI it seemed that replacing

subprocess.check_call(f'copy "{src_file}" "{dest_file}"', shell=True) with shutil.copy(str(src_file), str(dest_file))

helped. I'm not extremely code savvy so I'm not sure if it actually does pretty much the same or not. But if so it would be cool if you could change that, so that the program becomes more robust.

Sincerely, Dan

[thomasa88]

Hi, the code was in fact using shutil (specifically shutil.copyfile), but removed that. According to a comment in the code, shutil was very slow. https://github.com/thomasa88/ThreadKeeper/blob/d9272f881e9fc506d0b71e7f30bb4197fb5e3223/ThreadKeeper.py#L155-L156 I cant really say what slow means and if shutil.copy` is faster.

Do you have a copy of the error message? (Often Ctrl+C works on error dialogs, but not always..)