As far as I can see, appscript lacks an equivalent of Applescript's launch verb, which opens an app without running it (useful for apps like Textedit or Keynote that create default documents when they run). Did I miss something, or how can you open a file without the default run action? * * * * *
On Wed, Jul 19, 2006 at 11:29:45PM -0700, Robert Stephenson wrote:
> As far as I can see, appscript lacks an equivalent of Applescript's
> launch verb, which opens an app without running it (useful for apps
> like Textedit or Keynote that create default documents when they
> run). Did I miss
Robert Stephenson wrote:
> As far as I can see, appscript lacks an equivalent of Applescript's
> launch verb, which opens an app without running it (useful for apps
> like Textedit or Keynote that create default documents when they
> run). Did I miss something, or how can you open a file wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
has wrote:
> Robert Stephenson wrote:
>
>> As far as I can see, appscript lacks an equivalent of Applescript's
>> launch verb, which opens an app without running it (useful for apps
>> like Textedit or Keynote that create default documents when th
Kevin Walzer wrote:
> import os
>
> os.system('open -a TextEdit.app')
Still ends up sending a run event, unfortunately. The goal is to
launch the app without it opening an empty document, as 'launch app
"TextEdit"' does.
Ta,
has
--
http://freespace.virgin.net/hamish.sanderson/
__
Le 20 juil. 06, à 16:31, has a écrit :
> Kevin Walzer wrote:
>
>> import os
>>
>> os.system('open -a TextEdit.app')
>
> Still ends up sending a run event, unfortunately. The goal is to
> launch the app without it opening an empty document, as 'launch app
> "TextEdit"' does.
>
Try that :
Laurent Pierron wrote:
> Try that :
>
> os.system('osascript -e \'launch application "textedit"\'')
Yeah, calling AS is a last-ditch option, but I'm hoping someone'll
know how to do it via the Python standard library or an OS call.
(It'd be terribly ignominious for appscript to have to
Thanks, folks, I thought I might have missed something. I appreciate the suggestions and comments. You guys are great!- RobOn Jul 20, 2006, at 9:33 AM, has wrote:Laurent Pierron wrote: Try that : os.system('osascript -e \'launch application "textedit"\'') Yeah, calling AS is a last-ditch option,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to learn how to "freeze" an application that links against a
non-framework build of Python. The basic mechanism works fine when I try
a vanilla install of PPC Python 2.4 via Fink:
/sw/bin/python freeze.py hello.py
...lots of messages
make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like hacking the makefile generated by freeze.py solves the
problem. Copying the args from BASCFLAGS to CFLAGS results in a
universal binary.
CFLAGS=-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk
- -fno-strict-aliasing -Wno-long-
On Jul 20, 2006, at 9:54 AM, Kevin Walzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm trying to learn how to "freeze" an application that links
> against a
> non-framework build of Python. The basic mechanism works fine when
> I try
> a vanilla install of PPC Python 2.4
I found some time to rewrite the documentation for py2app to
correspond to 0.3.2, and I've made some minor updates since the 0.3.1
release.
The only change of real note in 0.3.2 is the changes I've made to the
py2applet script. It now supports taking --options, and there's a new
--make-set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Ippolito wrote:
>
>
> The other question is why the heck are you using a non-framework build?
Because I'm trying to package an application that builds against X11
Tkinter.
>
> You may have better luck with cx_Freeze than the built-in freeze t
On Jul 20, 2006, at 11:43 AM, Kevin Walzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bob Ippolito wrote:
>>
>
>>
>> The other question is why the heck are you using a non-framework
>> build?
>
> Because I'm trying to package an application that builds against X11
> Tkinter.
hi,
i was upgrading from a older version of py2app (pre-setuptools as far
as i know), following the instruction at http://svn.pythonmac.org/
py2app/py2app/trunk/doc/index.html#installation
using py2applet failed with:
> $ py2applet --make-setup myapp.py
> Traceback (most recent call last):
>
On Jul 20, 2006, at 12:32 PM, Kaweh Kazemi wrote:
> hi,
>
> i was upgrading from a older version of py2app (pre-setuptools as
> far as i know), following the instruction at http://
> svn.pythonmac.org/py2app/py2app/trunk/doc/index.html#installation
>
> using py2applet failed with:
>
>> $ py2ap
Hi folks,
I'm trying to get ctypes working on my new Macbook Pro under Python 2.4.
It works under Python 2.5beta, so I assume the porting work has been
done somewhere, but does not work with the downloadable version of
ctypes (libffi won't build):
> configure: error: "libffi has not been po
On Jul 20, 2006, at 1:22 PM, Dethe Elza wrote:
> Hi folks,
>
> I'm trying to get ctypes working on my new Macbook Pro under Python
> 2.4.
> It works under Python 2.5beta, so I assume the porting work has been
> done somewhere, but does not work with the downloadable version of
> ctypes (libff
Bob Ippolito wrote:
> I'm pretty sure that the version in Python 2.5 still has some i386 stack
> alignment bugs. Ronald has fixed them for PyObjC, but I don't think that
> work has migrated to ctypes yet.
>
> The version in http://svn.python.org/projects/ctypes/trunk/ctypes/ seems
> to be in sy
Hi,
I can start gui python apps by the command line
$: python whatever.py
or if I chmod u+x whatever.py then a simple
$: whatever.py
will do the job.
I am running python 2.4.3 on a mac ppc box with the lastest OS version.
I would like a quick way to start the app by either double-click a
*
On Jul 20, 2006, at 3:53 PM, Jerry LeVan wrote:
> Hi,
>
> I can start gui python apps by the command line
>
> $: python whatever.py
>
> or if I chmod u+x whatever.py then a simple
>
> $: whatever.py
>
> will do the job.
>
> I am running python 2.4.3 on a mac ppc box with the lastest OS
> versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Ippolito wrote:
>
> On Jul 20, 2006, at 11:43 AM, Kevin Walzer wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Bob Ippolito wrote:
>>>
>>
>>>
>>> The other question is why the heck are you using a non-framework build?
>>
>> Bec
On Jul 20, 2006, at 4:18 PM, Kevin Walzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bob Ippolito wrote:
>>
>> On Jul 20, 2006, at 11:43 AM, Kevin Walzer wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Bob Ippolito wrote:
>>>
The other ques
Bob Ippolito wrote:
On Jul 20, 2006, at 4:18 PM, Kevin Walzer wrote:
some fiddling in your main script if DISPLAY isn't set though.
If I were doing it I'd check for DISPLAY and look at the output of "/
usr/X11R6/bin/xauth list" to see if X11 is running.
Another option is some C code I found
Bob Ippolito wrote:
> That's kinda strange, maybe PythonLauncher is broken. I don't think
> anyone has paid attention to it in a few years.
Last I tried, it worked. The trick was to make sure that *.py files were
associated with. I don't remember how to do that, though.
> You might want to try
On Jul 20, 2006, at 5:03 PM, Christopher Barker wrote:
>
> Bob Ippolito wrote:
>> On Jul 20, 2006, at 4:18 PM, Kevin Walzer wrote:
some fiddling in your main script if DISPLAY isn't set though.
>> If I were doing it I'd check for DISPLAY and look at the output of
>> "/ usr/X11R6/bin/xauth
In article <[EMAIL PROTECTED]>,
Christopher Barker <[EMAIL PROTECTED]> wrote:
> Bob Ippolito wrote:
> > That's kinda strange, maybe PythonLauncher is broken. I don't think
> > anyone has paid attention to it in a few years.
> Last I tried, it worked. The trick was to make sure that *.py files we
On Jul 20, 2006, at 5:11 PM, Christopher Barker wrote:
> Bob Ippolito wrote:
>> That's kinda strange, maybe PythonLauncher is broken. I don't think
>> anyone has paid attention to it in a few years.
>
> Last I tried, it worked. The trick was to make sure that *.py files
> were
> associated with
thanks for the warning.
removed py2applet - i assume it was installed there by a previous
py2app version, right? (i saw that you already updated the
documentation accordingly to get rid of py2applet in http://
svn.pythonmac.org/py2app/py2app/trunk/doc/index.html#uninstalling-
py2app-0-2-x-or
hi,
using py2app 0.3.2 i encountered following problem.
WARNING: Mach-O header may be too large to relocate
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
python2.4/site-packages/py2app-0.3.2-py2.4.egg/py2app/build_app.py",
line 548, in _run
On Jul 20, 2006, at 6:17 PM, Kaweh Kazemi wrote:
> thanks for the warning.
>
> removed py2applet - i assume it was installed there by a previous
> py2app version, right? (i saw that you already updated the
> documentation accordingly to get rid of py2applet in http://
> svn.pythonmac.org/py2app/p
On Jul 20, 2006, at 6:23 PM, Kaweh Kazemi wrote:
> hi,
>
> using py2app 0.3.2 i encountered following problem.
>
>
> WARNING: Mach-O header may be too large to relocate
> Traceback (most recent call last):
>File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
> python2.4/site-packages
I used the get info dialog and set the app to PythonLauncher but it
did no good( even did a change all)
Any *.py file give a "Can't open *.py" error message...
Jerry
___
Pythonmac-SIG maillist - [email protected]
http://mail.python.org/mail
33 matches
Mail list logo
