On Dec 28, 2010, at 12:24 PM, Aahz wrote:
> Nope. If you're doing that, just use os.path.exists() or isfile().
> Faster and safer.
I was hoping that I could detect it no matter where it was so advanced users
could do symlinks or move it to their own folders or whatever which made me
think of
On Tue, Dec 28, 2010, Adam Morris wrote:
> On Dec 28, 2010, at 12:46 AM, Christopher Barker
> wrote:
>
>> I think you could specifically search for the utility in places it
>> might be expected to be found:
>>
>> /usr/bin
>> /usr/local/bin
>> /sw/... (for fink)
>> /opt/... (for macports)
>
> Th
On Dec 28, 2010, at 12:46 AM, Christopher Barker wrote:
> I think you could specifically search for the utility in places it might be
> expected to be found:
>
> /usr/bin
> /usr/local/bin
> /sw/... (for fink)
> /opt/... (for macports)
That's the first thing I tried; maybe I typed wrong? I'll gi
Adam Morris wrote:
Could this be a problem with py2app, or is there something about the
run-time environment I've overlooked?
Would also be interested if there is a better way of checking to see
if a command line utility is currently located in the path for the
current user's system.
I think w
py2app experts,
I have a script that is packaged using and py2app that does a
pre-check to see if a command line utility is installed, using Popen
and "which name". (The script downloads and installs it if not.)
I pass subprocess.PIPE for stdout and stderr, with shell=True.
When I run the script
