I am using SSH to execute a script remotely. I have executed this script many many times in the past using the command:
/path_to_env/bin/python3 “/absolute_path_to_script_directory/script.py” --cfg "/absolute_path_to_config_file/config.yaml" wandb.use False
But out of nowhere, when I tried to execute the above command today, I received the following error:
/path_to_env/bin/python3: can't open file '/absolute_path_to_current_directory/“/absolute_path_to_script_directory/script.py”': [Errno 2] No such file or directory
Why is python suddenly trying to prepend the path to my current directory in front of the absolute path I am specifying in terminal? I am running the same exact command that I have used hundreds of times with no issue; this issue has really come out of nowhere. Can anyone provide an explanation?
I am able to run the script by removing all quotation marks:
/path_to_env/bin/python3 /absolute_path_to_script_directory/script.py --cfg /absolute_path_to_config_file/config.yaml wandb.use False
I am just really curious as to why using quotation marks worked when I ran this script yesterday (and everyday before today), but it doesn’t work now?