3 ms·
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.
by 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 agoHe may be referring to binfmt.
- emmelaich 15y agoI 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 agoI agree, as evidenced by the bit you didn't quote. (?!)