Thanks, But - won't this still require me to set the environment variable one at a time? Can I not pass the entire user environment to launchd? I'm running the job as a User LaunchAgent, so I don't understand why this would not be the default behavior. Damien Sorresso wrote:
Use `launchctl setenv <name> <value>` from within your Python script.
See launchctl(1) for more. -- Damien Sorresso BSD Engineering Apple Inc.
_______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
-- View this message in context: http://old.nabble.com/Launchd-sanitizing-python-environment-tp26799801p26850... Sent from the Launchd mailing list archive at Nabble.com.