On 10 Sep, 2009, at 12:09, Georg Seifert wrote:
If you want to make absolutely sure that Apple can't break you, you
could bundle the version of Python.framework upon which you depend
into your app. However, that's probably not necessary unless you
want to use a newer version of Python t
On 14 Sep 2009, at 16:28, Bill Janssen wrote:
has wrote:
You can install appscript from source using plain old distutils; the
setup.py script will use setuptools if it's available and distutils
if
not. Though if there are problems with setuptools then I'd suggest
filing bug reports on tha
has wrote:
> On 13 Sep 2009, at 18:52, Bill Janssen wrote:
>
> > Is it possible to disentangle appscript from setuptools? I just
> > downloaded the sources to my Snow Leopard machine, did
> >
> > python setup.py build
> > python setup.py install
> >
> > which went just fine. But then I did
> >
UPDATE: Sorry, I was wrong. Client and server are equal in this
respect. Look:
geert-dekkerss-macbook-pro:~ geert$ file /System/Library/Frameworks/
Python.framework/Versions/2.5/Python
/System/Library/Frameworks/Python.framework/Versions/2.5/Python: Mach-
O universal binary with 4 architectur
Thanks David. As you suggested, I did a "file" on a python executable,
and found that while you are quite correct that python is compiled a 2
way binary on a client 10.5, it's already a 4 way binary on the new
xserve I have running 10.5 even though it's version 2.5. I also
discovered that
On 13-Sep-09, at 10:58 AM, Geert Dekkers wrote:
The problem is of course that I need to coax PyObjC to be run by 64
bit Apache. I read about the ability for PyObjC to run in 64-bit
mode athttp://pyobjc.sourceforge.net/documentation/pyobjc-core/news.html
. I don't know where to find out if my
