hari jayaram wrote:
In my several tests over the last few days. I can definitely say that
without forcing the standalone build , when I used the python from
python.org ( both 2.5.5 and 2.6.3) . py2app never created a standalone
build. It bundles the required libraries but never includes the syste
Thanks for your emails ..
In my several tests over the last few days. I can definitely say that
without forcing the standalone build , when I used the python from
python.org ( both 2.5.5 and 2.6.3) . py2app never created a standalone
build. It bundles the required libraries but never includes the
Kevin Walzer wrote:
I wonder if the problem is with py2applet and the build script it
generates?
Maybe, you seem to be making this more complicated than it should be.
This should do it:
from setuptools import setup
APP = ['GridZilla.py']
DATA_FILES = []
OPTIONS = {'argv_emulation': True,
Ronald Oussoren wrote:
Is anyone interested in helping to create a testsuite for py2app?
The first priority would be to have some blackbox tests, unittests can
be added later.
good idea.
The testcases would be simple applications with a
setup.py and a verification script. Testcases should
On 10/14/09 10:45 AM, hari jayaram wrote:
My py2applet build_app.py script has the following line in line 911
pydir = 'python%s'%(info['version'])
When I force a standalone build, the Frameworks directory has no
Python.Framework
The info.plist is setup correctly with the value :
@exec
My py2applet build_app.py script has the following line in line 911
pydir = 'python%s'%(info['version'])
When I force a standalone build, the Frameworks directory has no
Python.Framework
The info.plist is setup correctly with the value :
@executable_path/../Frameworks/Python.framework/Ve
