12 Jun
2019
12 Jun
'19
9:25 a.m.
On Wed, Jun 12, 2019 at 9:59 AM Bailey, Henry Albert (Al) <Al.Bailey@windriver.com> wrote:
For cases where we created custom python scripts using /usr/bin/env, it's likely because google/stackoverflow indicate that's the preferred way. There's no specific reason to code it that way, as far as I can remember.
Outside of a distro context the biggest reason I do that (use #!/usr/bin/env) is to make using virtual environments easier. I do not think that is a large concern here, the first place I could see it coming up is running in DevStack with virtual envs enabled, which is not as much of a thing as it should be and probably doesn't work now anyway. dt -- Dean Troyer dtroyer@gmail.com