I know they are set in my profile etc and it runs on the Mac. I have certain variables set on all machines I use, Windows, Solaris, Linux and Mac, so when I run my scripts they don't need editing they just pick up the variables.
The action would just error out, there is some checking for arguments in the script, so I left them out and the program would run, this was starting to annoy me, but after a little Google-Fu I saw an post about environment variables in a python script not being picked up. Python /path_to_script/create_conf_files.py -services Python /path_to_script/create_conf_files.py -sas In automator I had selected Run Shell script, I had selected /bin/bash (default) as my shell, changed Pass Input to As arguments then added the lines When I setup the command in Automator, it would not run. I wanted to set this up in Automator as I want it scheduled, and I was going to schedule the Application to run via iCal. I knew my Python script ran OK from the Terminal as I have been running this for a while, I just call the script and the arguments and everything was good. I dynamically create the configuration files so when I add new ones, I don't need to edit anything it will just run. The script basically creates separate config files that my backup script scrolls through and then backs them up to my Dropbox.Ĭurrently I backup my Automator apps, Automator workflows, saved searches etc. AutomatorRecently I was trying to schedule a Python script to run on my Mac.
0 kommentar(er)
