On 8-Jun-2007, at 13:19 , has wrote:
You might add a note that since findertools uses aetools which is
[over]due for deprecation, findertools should be deprecated as well.
[...]
Or you can do it with appscript if you prefer:
from appscript import *
from mactypes import Alias
Ronald Oussoren wrote:
Using subprocess is much better because you don't have to worry about
quoting for the shell. Os.popen and os.system should basically be
deprecated, but that will probably not happen anytime soon because they
are used a lot in existing code.
>
I use os.popen because i
On Friday, June 08, 2007, at 02:57PM, "Kent Johnson" <[EMAIL PROTECTED]> wrote:
>has wrote:
>> Anyway, simplest solution here is:
>>
>> import subprocess
>> subprocess.call(['open', '/Users/drew/Documents'])
>
>or
>import open
import os # ;-)
>os.system('open /Users/drew/Documents')
T
has wrote:
> Anyway, simplest solution here is:
>
> import subprocess
> subprocess.call(['open', '/Users/drew/Documents'])
or
import open
os.system('open /Users/drew/Documents')
Kent
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
h
Ronald Oussoren wrote:
>> i was wondering if anyone else has seen this behavior with the
>> findertools.launch() function. the docs indicate that when given a
>> pathname, launch(path) will launch a Finder window with that path.
>> but
>> when i try to launch any valid path i get this error:
>
>
On Friday, June 08, 2007, at 09:55AM, "Drew Houston" <[EMAIL PROTECTED]> wrote:
>hi there,
>
>i was wondering if anyone else has seen this behavior with the
>findertools.launch() function. the docs indicate that when given a
>pathname, launch(path) will launch a Finder window with that path. bu
hi there,
i was wondering if anyone else has seen this behavior with the
findertools.launch() function. the docs indicate that when given a
pathname, launch(path) will launch a Finder window with that path. but
when i try to launch any valid path i get this error:
>>> os.path.exists("/Users/d
