4 ms·
I use Python for my scripting needs. It is a little bit more cumbersome to call unix tools from a Python script, but handling strings and arguments and things l
by adrianN 13y ago
I use Python for my scripting needs. It is a little bit more cumbersome to call unix tools from a Python script, but handling strings and arguments and things like that is so much easier. I feel like bash is really weird for anything longer than a for loop.
Can someone please provide some arguments why I should write bash scripts instead of Python scripts?
- btilly 13y agoMy experience is that bash is faster and easier for below 20 lines. But if things grow, you'll wish you had used a real scripting languages. All useful tools grow.
- danellis 13y agoIt's not really about LoC, it's about what you're trying to do. If what you're doing is, essentially, job control, then Bash is still easier than Python. But not for much else, and Python is very widely available these days.
- btilly 13y agoMy experience is that job control in Perl and Ruby is almost as easy as bash, plus you have a real programming environment to fall back on. My experiences with job control in Python were admittedly not quite as pleasant.
- terhechte 13y agoSame here, I could never relate to bash's specific syntax, so I just started to do everything in Python. I'm thinking about fully switching to Julia for this though, as it offers an easier way of integrating Unix commands.
- e12e 13y agoPersonally I use bash when I need to, well, script shell commands. Anything that is reasonably described as series of shell commands, filter/pipes. There are a lot of best-practices that one need to adapt though, and there's definitively a learning-curve. Generally scripts should work under things like dash, and not be bash-specific. That means delegating some work to sed/grep/awk (or being really "clever"). I've found that using functions, and passing arguments rather than setting (global) variables help a lot -- and if you get to the point that you really want do debug, you're better off rewriting in something like python. I've never liked perl -- it's always seemed like a bit of a pointless exercise in moving side-ways rather than "up". I've never had to move away from shell scripts out of performance needs, only out of maintenance needs -- and for me perl buys me nothing in that direction. Now, things like fabric[f] can make sense -- but the benefit of (ba)sh is that it's guaranteed to be there (on a nix platform) -- and it is great for bootstrapping. I'm not* a fan of how some projects use (ba)sh, though. The ones that list instructions like these (and there have been a few lately): curl http(s)://great-tool.com/install | sudo bash They often a) don't use https and b) require sudo/root blindly (rather than at least wrapping what needs sudo in something like: prompt -p "Need superuser permission for apt-yum-install libfoo [y/n]: " ans if [ "${ans}" == "y" ]; then sudo apt-yum-install libfoo else echo "Aborted." exit 1 fi Which generally works rather painlessly -- and could be further "automated" by allowing a --yes-go-ahead, or checking if the script is running as root. [f]: http://fabfile.org http://fabfile.org
- dfc 13y agoIf you are worried about dash compatibility I hihly recommend checkbashisms: http://packages.debian.org/sid/devscripts http://packages.debian.org/sid/devscripts