5 ms·
I've tried that path with little success. Usually, arg parsing makes me try some other language (perl, python) but other things got complicated there, mostly ru
by lysium 6y ago
I've tried that path with little success. Usually, arg parsing makes me try some other language (perl, python) but other things got complicated there, mostly running other processes, capturing their exit status, pipe-ing their output etc.
In the end, it was easier to hammer onto bash. Also, there are great linters for bash scripts, so things work out.
- IggleSniggle 6y agotcl is designed for this situation
- lysium 6y agoThx, I’ll give it a shot!
- lou1306 6y ago> but other things got complicated there, mostly running other processes, capturing their exit status, pipe-ing their output Note that Python's subprocess module [0] has received many updates since v3.5, and now I find it relatively painless. Most of the times, subprocess.check_output() or subprocess.run() will do the trick. [0]: https://docs.python.org/3/library/subprocess.html https://docs.python.org/3/library/subprocess.html
- lysium 6y agoThx, I’ll check it out again!
- kortex 6y agoI've been in a similar boat, yet despite as my experience with it grows, bash just wears on me. Everything feels like a hack. Sure, piping is easy, but if statements are atrocious. Starting to get into Xonsh. Still a learning curve, cause it's neither bash nor python, but it's really refreshing.