Very true, but that also depends on the context. For virtualenv + python as a general rule, it is best to do:
#!/usr/bin/env python
Something that isn't pointed out is that people who aren't ok with this move don't have to use Fedora / a systemd distro moving to this model. They could fork fedora or build their own distro. It isn't as though distributors are forcing a free distro down your throat :)
Posted Feb 28, 2012 17:43 UTC (Tue) by drag (subscriber, #31333)
[Link]
anything other then "#!/usr/bin/env python" is essentially broken, unless your specifying a specific python version, in which case it should be "#!/usr/bin/env python2.8" or whatever.
Various notes on /usr unification
Posted Feb 28, 2012 20:39 UTC (Tue) by lindi (subscriber, #53135)
[Link]
seems to give quite opposite advice at least for official debian packages:
"Maintainers should not override the Debian Python interpreter using /usr/bin/env python or /usr/bin/env pythonX.Y. This is not advisable as it bypasses Debian's dependency checking and makes the package vulnerable to incomplete local installations of python."
Various notes on /usr unification
Posted Feb 29, 2012 16:10 UTC (Wed) by cortana (subscriber, #24596)
[Link]
That document is aimed at Debian package maintainers. Stuff shipped by Debian is supposed to to use Debian's own Python interpreter, hence hacks like running python via env are not permitted.
Various notes on /usr unification
Posted Feb 28, 2012 20:43 UTC (Tue) by samroberts (subscriber, #46749)
[Link]
I think env itself is /bin/env instead of /usr/bin/env on some unixen, though it might be in /usr/bin for all linux distros, which makes it the kind of thing the unification might help.