Thank you for your fixing. I merged it into my branch and PyPI

Thanks!

I'm sorry that I don't know any technical details as to why, but having shell=True breaks the "command" command for OS X.

I'm not sure if there is a more system independent way to check for the existence of a JavaScript runtime, or if there would need to be some system detection logic to determine how to execute the "command" command.

ugh. To be honest, I ran into further issues with finding runtimes, but didn't have time to author a clean fix and offer a pull request. I forked PyExecJs and did what local hacks I needed to get things going and left it as it is. If @doloopwhile (or anyone else) is interested in fixing this, I suggest implementing a pure-Python implementation of which/command - all it has to do is iterate environ['PATH'].split(':'), looking for the runtime in each.

I took a stab at it...

https://github.com/mattjmorrison/PyExecJS/commit/146465ac7ac6d2ee52da4720e1c17b702fb3ab5d

I tried it on Mac OS X and Ubuntu 11.10 and it seemed to work with Node.js installed for both.

I pushed new commit. It includes a implementation pure Python "which" based on your idea.
Thanks you !

I really did very little, no sweat.