you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 years ago* (5 children)

I can't think of a single reason to use bash over Python. Anything you can do in bash can be done in pure Python. Unless you're working in some embedded environment it's a non-issue to install a Python interpreter (you certainly already have one). I would only use sh/bash for packages I'm distributing to avoid the external dependency, and then only if it's a relatively simple script.

  • source
  • hideshow 10 child comments
  • [–] 19 points 3 years ago (1 child)

    I know whatever environment I run my shell script in has sh, I can't rely on (the right version of) python being there.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -6 points 3 years ago (1 child)
  • [–] 6 points 3 years ago (1 child)

    Because you could be on another machine that doesn't have Python 3.X it only has 3.X-1. or you could write code for Python 3.12 and then four years later no one has 3.12 anymore.

    Sometimes you need to download packages from pip but pip might not be available or you may be hitting your company's internal pip mirror.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -2 points 3 years ago (1 child)

    How often are you writing scripts that accidentally require a specific minor version of Python 3 to run? If you have dependencies, 1) you're no longer scripting, and 2) you need to manage your runtime environment anyway.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 3 years ago (1 child)

    Runtime environments can change often, if you need to install your application on a ton of PC's you don't want to install python version 3.X on all of those instead you could just compile it into a native binary, pip is the most unsafe hell

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 3 years ago (2 children)

    i would not run a python script with root.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 9 points 3 years ago (2 children)

    Why is always about bash? POSIX shell scripts run everywhere.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 3 years ago (1 child)

    BASH has some useful features and I’ve literally never had an environment with bash unavailable (even if a package is needed, so what).

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 years ago (1 child)

    Python is superior for string anything (parsing, searching, manipulating). But Bash is much simpler for running existing CLI tools. Plus you should already be using Bash as a simple terminal language already, so wrapping what you're used to into a simple script flows naturally.

    Eg, if I have some admin tool for updating a user thingamajig, a common scripting need is just running that tool for every user in a file (or the output of another command). The string manipulation that often requires is annoying in bash, but running the commands is easier than Python.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago

    If what you're doing is essentially a few shell commands, then you may as well put it into a script. If you're talking about how "elegant" your shell scripts are and comparing them to Python, you're probably wrong and should be using Python.

  • source
  • parent