Erik Max Francis wrote: > The file _is_ a /bin/sh executable. You're just having that /bin/sh > executable run something else -- how could `file` figure that out > without a ridiculously complicated set of rules that rise to the level > of a sh interpreter -- thereby, defeating the purpose?
but... $ cat test.py #!/usr/bin/env python print "Hello, world" $ file test.py file.py: a python script text executable following what you said, test.py is a /usr/bin/env script, not a python one. -- Under construction -- http://mail.python.org/mailman/listinfo/python-list
