Closed benyanke closed 7 years ago
I think it's a problem of string interpretation (the "" are removed by the shell, but here they seem to be preserved and the path synchronized seem to be literally "Art Department/M00001000 - M00001999"
). Can you try with a path that does not need to be quoted?
Thank you so much! I got it working by simply removing the quotes. Turns out the subprocess.popen module doesn't require any quotes or escaped spaces, because it passes array entries as arguments directly, so there's no issue of spaces being confused for the end of the argument.
In case anyone is curious, I just finished v1.0.0 of UnisonCTRL, my unison wrapper script for handling large datasets which I mentioned above.
I'm currently using it on my 1.9 TB, 1.1 million file dataset to achieve sub-minute sync latency.
Nice!
When starting unison instances from a python script (using subprocess.popen w/ shell=false), I am unable to detect any changes. However, when running the same commands in my shell directly, or with shell=true, it works.
I suspect this may be something to do with the environment, but I'm not sure. I am not using any config files, all options are being specified directly as arguments. One such command and it's debug logs:
Logs:
Any ideas?