5 ms·
#!/usr/bin/env python2 There, fixed it. Much like `#!/usr/bin/env bash` for bash scripts instead of `#!/bin/bash` (which won't work on many OSes) https://git
by moviuro 9y ago
#!/usr/bin/env python2
There, fixed it.
Much like `#!/usr/bin/env bash` for bash scripts instead of `#!/bin/bash` (which won't work on many OSes)
https://github.com/search?q=%23%21%2Fusr%2Fbin%2Fenv+python2&type=Code https://github.com/search?q=%23%21%2Fusr%2Fbin%2Fenv+python2...
- saurik 9y agoYou can't "there fixed it" for the infinite number of projects that exist in the field that this breaks. "It never worked on FreeBSD" is very different from "it no longer works on new versions of RHEL".
- throwaway2048 9y agoif changing a hashbang is that big of a deal, the codebase is completely mortibund going forward, and support is dropping in 2020 anyways. I don't think people should be concerned about people that are that totally resistant to change.
- Sir_Cmpwn 9y ago>You can't "there fixed it" for the infinite number of projects that exist in the field that this breaks Of course you can. Python files are plaintext. $ find ./some/module -name "*.py" -exec sed -e 's:#!/usr/bin/python:#!/usr/bin/env python2:g' -i {} ;