5 ms·

Maybe because it's a hack because to get around the following not working? #!python

• emmelaich 15y ago
  Yes; #!python should be made to work. Not to use the user's PATH, but some system ordained python (via some kernel work). env is a hack.
  • rbanffy 15y ago
    > via some kernel work Kernels shouldn't be aware of the search path shells use.
    • nodata 15y ago
      He may be referring to binfmt.
      • emmelaich 15y ago
        I wasn't referring to implementation really, but the principle. The main python could be in /bin or /usr/bin or possibly /usr/local/bin. The poor user or developer shouldn't be required to anticipate where and should not need to resort to hacks such as env.
    • emmelaich 15y ago
      I agree, as evidenced by the bit you didn't quote. (?!)
• rbanffy 15y ago
  Bad idea. Which python (or program named "python") will run your script?
  • deleted 15y ago
    [deleted]
  • nodata 15y ago
    The first python in your path would run the script.
    • rbanffy 15y ago
      So, if your PATH gets changed, say, by something that just lept out of your web browser's sandbox, that's the python that'll run your your scripts, right?
      • nodata 15y ago
        Yes, that's how it would work, same as with env.