At the moment ashes.py starts with no #!, although it also supports running as script.
Thus, if one downloads the latest release, and just makes the ashes.py executable, and then tries to run it, the OS will invoke it by using sh as the interpreter. (Which yields quite some strange behaviour if one has installed ImageMagick, because import is a valid command.)
By adding #!/usr/bin/env python as the first line of the ashes.py it behaves as expected (i.e. running with the right interpreter), and in the worst case scenario (although this #! is the generally accepted one for Python) it would just fail without interpreting the rest of the Python code as shell code.
At the moment
ashes.pystarts with no#!, although it also supports running as script.Thus, if one downloads the latest release, and just makes the
ashes.pyexecutable, and then tries to run it, the OS will invoke it by usingshas the interpreter. (Which yields quite some strange behaviour if one has installed ImageMagick, becauseimportis a valid command.)By adding
#!/usr/bin/env pythonas the first line of theashes.pyit behaves as expected (i.e. running with the right interpreter), and in the worst case scenario (although this#!is the generally accepted one for Python) it would just fail without interpreting the rest of the Python code as shell code.