Earlier quoted context omitted.
Xonsh is a shell that integrates Python at the command line. This is a library to make calls to the command line.
And your point is??
"Xonsh is " NOT " how to do this."
11–20 of 54 posts
Anyone know how the name came about?
I've been using 'tentakel' for remote server admin for years, 'fabric' for lightweight deployment, and more recently 'invoke' for local invocations (all are Python projects). This project looks interesting too, will give it a try. BTW: Has anyone news on Fabric 2 ?
s(command_from_potentially_unsafe_source).run()
compare with os.system(command_from_potentially_unsafe_source)
or subprocess.call(command_from_potentially_unsafe_source, shell=True)
securitywise? I'm assuming all three are equally bad?How does s(command_from_potentially_unsafe_source).run() compare with os.system(command_from_potentially_unsafe_source) or subprocess.call(command_from_potentially_unsafe_source, shell=True) securitywise? I'm assuming all three are equally bad?
How does s(command_from_potentially_unsafe_source).run() compare with os.system(command_from_potentially_unsafe_source) or subprocess.call(command_from_potentially_unsafe_source, shell=True) securitywise? I'm assuming all three are equally bad?
I looked at the source code. Under the hood, it's just a thin wrapper around `subprocess`.
Which was super useful for controlling some utilities that wanted to be run in an interactive bash shell.
+1 for https://sultan.readthedocs.io/en/latest/sultan-examples.html...
I think it would be interesting if you could iterate on the results of "ls -l", where each row is represented by an object.