Ned Deily wrote: > In your first posting, your script was written using /usr/bin/env: > > #! /usr/bin/env python > > That leaves you at the mercy of whatever PATH has been set to.
> Suggest you change the cron table entry to explicitly invoke the python > you want, so (all on one line, of course): or change the #! line to the one you want: #!/usr/local/python2.5 or #!/Library/Frameworks/Python.framework/Versions/2.5/bin/python I like to do that anyway with production code, as it makes it clear which python the script was tested against. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
