On Sun, 23 Oct 2016, Stuart Henderson <[email protected]> wrote: >> #!/usr/bin/env python > > Opinions vary but I'm not a fan of using env for this, I don't normally > want to trust the first file of that name found in the path.
There are two kinds of people: those that know exactly what their $PATH is, and those who don't - the 99%. Those who do know, are almost certainly well aware that 99% of one-off scripts in the world use #!/usr/bin/env, and don't put an executable named "python" in their $HOME/bin - or accept the consequences. Those that don't know, are probably running OSX, or Windows, or some random minty flavor of Ubuntu - and there is NO way to predict or establish the location of the Python executable. Everyone wants to "just move on with the work", I guarantee my coworkers would throw rocks at me if I tried to get them to use setuptools. > Can you just use setuptools? That generally does the right thing. When distributing a library or a package - yes, the sanest thing to do. When working with a bunch of frontend developers that try a "sudo curl | bash" when "curl | bash" doesn't work - no, you can't let them hurt themselves, you must use whatever method has the smallest chance of making them shoot themselves in the foot. You want them alive, so they can deal with that Node.js stuff - so you don't have to. <3,K.
