exiftool command line changes atomic operation order

~/mambaforge/envs/micasense/lib/python3.7/subprocess.py in init(self, args, bufsize, executable, stdin, stdout, stderr, preexec_fn, close_fds, shell, cwd, env, universal_newlines, startupinfo, creationflags, restore_signals, start_new_session, pass_fds, encoding, errors, text) > 339 with Popen(*popenargs, **kwargs) as p: ~/mambaforge/envs/micasense/lib/python3.7/subprocess.py in call(timeout, *popenargs, **kwargs) > 358 retcode = call(*popenargs, **kwargs) ~/mambaforge/envs/micasense/lib/python3.7/subprocess.py in check_call(*popenargs, **kwargs) After trying for 4 hours to forensically investigate this problem (because I'm new to exif), I have determined that it's a problem with Jupyter and not exiftool: I know this because I just successfully updated the metadata for all 355 tiffs in the 'stacks' folder using the terminal.ĭoes anyone have any idea what's causing this strange behavior in Jupyter?įileNotFoundError Traceback (most recent call last) I'm also running the batch processing tutorial, and I get a 'No such file or directory' error when I try to run the exiftool -csv line from a Jupyter notebook (running on a Mac).

Exiftool command line changes atomic operation order