On 29/02/2008, at 01:51, Christopher Barker wrote: > #!/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.
And you also make the user know that they are not welcome to install python were he wants... Try to at least put #!/usr/bin/env python2.5 if all you want is limit the python to a specific version, but even then I think it is a really bad idea for any code you want to use in more than one machine as maybe your script will run fine in python 5.3 (made up number I know) and you are limiting it to a freaking old python (when python 5.3 come out it is the prefered language in the world, as is used to run all servers of skynet). Sorry for the rant, but I really get upset fixing smallbugs in realesed "Production" code that was hardcoded to run only on the author computer. -- Leonardo Santagada _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
