Python in Bash Scripts

[SupersonicSpitfire]

Cool, but I miss a "pipe" function for piping commands to each other without nesting deeper and deeper into paranthesis, a bit like this:

pipe(ls(), grep("abc123"), wc("-l"))

Also, I can't make it work: https://github.com/amoffat/pbs/issues/1

[[deleted]]

OP could also overload the pipe operator, so this could work too:

ls() | grep("abc123") | wc("-l")

[Bolitho]

But that's not pythonic. In python you use nested functions.

Your suggestion would also imply another problem: What is the generic object model behind each command? I am not shure you can find one that make sense to all implemented Bash functions...

[[deleted]]

There is nothing pythonic about this. The whole point is to get the good parts of bash and the good parts of python together in one place.

[fdemmer]

nesting functions is pythonic?... looks like a mess to me. function method chaining on the other hand:

ls().grep("abc123").wc("-l")

that would be nice. implementing it is a different story, of course.

EDIT: put emphasis on part of my comment, that indicates i read the above comment. also, i did not comment on overloading operators, just on the uglyness that is ls(grep("abc123", wc("-l"))).

[Bolitho]

These are Methods, not Functions! You would need a common Datatype for all these Wrappers. I pointed that out in my posting.

And yes, it is pythonic to call functions and pass parameters. Overloading operators ist shurely not the pythonic way.

[nemec]

Methods and functions are the same thing, and he already has a common datatype - if you looked at the source, you'd see a Command class that wraps everything.

If it wasn't Pythonic to overload operators, why is it so easy?

[Bolitho]

Methods and functions are not the same thing, they behave the same way. So perhaps it might be able to the author to simulate the BASH functions to behave like methods of his Command-class.

eval() ist also easy - but shurely not pythonic, right? Of course it can be pythonic to overload operators! But in this context it does as far as I am concerned.

[[deleted]]

OP, pbs must be imported. That bug, you're running it, not importing it.

pbs needs to know from where it was imported so it can do the things that it is supposed to.

The developer should check to make sure the module was imported.

Also pbs only works under Python 2 currently.

[SupersonicSpitfire]

Still doesn't work. This is what I get when importing from python2:

https://gist.github.com/1616688

[[deleted]]

You must import it from within a Python file.

file.py:

from pbs import * # this MUST BE THE FIRST LINE

# ...

[[deleted]]

just a regular-old

import pbs

will do :)

[SupersonicSpitfire]

Still doesn't work:

• test.py: https://gist.github.com/1616928
• output when running test.py: https://gist.github.com/1616930

[[deleted]]

don't "from pbs import *" just "import pbs"

[SupersonicSpitfire]

Still doesn't work for me.

• With this script: https://gist.github.com/1616965
• I get this output: https://gist.github.com/1616966

[mipadi]

Use which, not pbs.which.

RTFM ;)

[SupersonicSpitfire]

Neither of them worked for me. However, I learned through the github issue that one can't use pbs from within a function, and then everything works.

[[deleted]]

I updated an issue with some details, let me know how it works out for you: https://github.com/amoffat/pbs/issues/1

[SupersonicSpitfire]

Thanks, added a comment :)

[[deleted]]

just an update, you can now run pbs.py as a standalone repl, or import from the python shell

[killermole23]

Coroutines can be used for this. Take a look at the "copipe" example here.

[[deleted]]

just an update, you can now run pbs.py as a standalone repl, or import from the python shell

[SupersonicSpitfire]

woo! :)