#!/bin/bash
#!/usr/bin/python
as they're not guaranteed to live there. That's what /usr/bin/env is for - to provide the path to wherever it really does live, and it is much more likely to exist where you might expect. So:
#!/usr/bin/env bash
#!/usr/bin/env python
Interesting, I wasn't aware of that.But /bin/bash is the way I've been writing bash scripts for almost three decades, long before /usr/bin/env was ever a thing, and it hasn't - yet - let me down. And frankly, I'd be surprised if support for it was completely dropped on any of the mainstream distros since it's a very very entrenched habit and a lot of existing scripts and full programs will fail if /usr/bash goes away. I've found more systems where only sh was available, but that's obviously less powerful at scripting and normally an edge case except in containers.
BTW, AI had no hand in my use of them, so it's not directly related..
But I don't disagree with new standards and do not disagree that may be useful and, after I've checked on the systems I maintain, I may adopt it. Thank you.
(Kind of amused that a three line bash script can trigger such contention...)
