Do you do any scripts beyond extremely simple ones?
I do a fuck ton of scripting in both bash and python. I never want to do string manipulation in bash. As soon as string manipulation is required, I automatically choose python for a script. Also, if I need named arguments or multiple levels of arguments for subcommands. You can use sys.argv for basic args, which isn’t any harder than bash arguments, but for complex inputs, argparse is a godsend. It has a bit of a learning curve, but it can handle anything. Bash requires you to write complex arg handling manually with loops and reducing.
You should check out Click. Way more user friendly than argparse imo. I agree with all of your points though, and I’d also add if you are working on a team that it will be infinitely easier for a co-worker to decipher your python code compared to a bash script. And you can write unit tests with py test, the list goes on and on. If the environment you are deploying to has the python interpreter, you should use python over bash.
I’ll take a look at Click. Something better than argparse definitely piques my interest, because while the features are great, it feels a little cumbersome at times.
Tbh you’d still be better off writing them in python. They’ll be more maintainable, and you’ll learn valuable skills.
Also, since you commented that python was the slowest language ever, shell scripts are often significantly slower. This is due to the fact that shell commands are actually calling other programs, which is very very slow.
Do you do any scripts beyond extremely simple ones?
I do a fuck ton of scripting in both bash and python. I never want to do string manipulation in bash. As soon as string manipulation is required, I automatically choose python for a script. Also, if I need named arguments or multiple levels of arguments for subcommands. You can use sys.argv for basic args, which isn’t any harder than bash arguments, but for complex inputs, argparse is a godsend. It has a bit of a learning curve, but it can handle anything. Bash requires you to write complex arg handling manually with loops and reducing.
You should check out Click. Way more user friendly than argparse imo. I agree with all of your points though, and I’d also add if you are working on a team that it will be infinitely easier for a co-worker to decipher your python code compared to a bash script. And you can write unit tests with py test, the list goes on and on. If the environment you are deploying to has the python interpreter, you should use python over bash.
I’ll take a look at Click. Something better than argparse definitely piques my interest, because while the features are great, it feels a little cumbersome at times.
I’m trying to bash it but the problem persists. Please help.
deleted by creator
Tbh you’d still be better off writing them in python. They’ll be more maintainable, and you’ll learn valuable skills.
Also, since you commented that python was the slowest language ever, shell scripts are often significantly slower. This is due to the fact that shell commands are actually calling other programs, which is very very slow.