3

I am using buildout to create a local python environment, and then using the local python to create my app with py2app. But, when I go into the .app file, specifically into Contents/MacOS/, there is just a shortcut to the system python. I want py2app to somehow take the local python with it so that it only depends on itself, not on the system python.

So my question is: How can I fix this so that py2app will bundle my custom local version of python2.7 so that my app will be totally standalone, regardless of the local python version?

Please let me know if more information would be helpful.

My setup.py

from setuptools import setup

APP = ['main.py']
DATA_FILES = ['src/icon.xib']
OPTIONS = {
            'argv_emulation': True,
            'packages': [ 'requests' ],
            'iconfile':'src/myApp.icns',
            'plist': {'CFBundleShortVersionString':'0.1.0',
                      'LSUIElement': True
                     }
          }

setup(
    name='myApp',
    package_dir = {'':'src'},
    app=APP,
    data_files=DATA_FILES,
    options={'py2app': OPTIONS},
    setup_requires=['py2app'],
)
icodebuster
  • 8,890
  • 7
  • 62
  • 65
vik
  • 300
  • 1
  • 12
  • http://www.stackoverflow.com/questions/10184974/py2app-is-not-copying-the-python-framework-to-the-new-app-while-using-virutalenv is a bit similar. It might get you somewhere. – kirbyfan64sos Jul 11 '13 at 15:42
  • right, i saw that before. Is what I'm doing (using a local python from buildout) different than what is described in the solution there? I'm not creating the app with the system python, i'm using my local python – vik Jul 11 '13 at 15:44
  • Hmm...according to the py2app website, a non-standalone build should only happen if the -s option is enabled. – kirbyfan64sos Jul 11 '13 at 15:58
  • so by default, it should be creating a totally standalone .app file? – vik Jul 11 '13 at 16:00
  • 1
    Well, it seems that way. According to some research I did, some py2app builds accidently enable that option. Verify you have the latest version. Also, are you absolutely sure you are calling the local Python from the terminal? Can you try not using virtualenv? – kirbyfan64sos Jul 11 '13 at 16:05
  • if i run python in the terminal, lots of my imports fail. The same imports work when i try in my local python interpreter, so I'm pretty sure i have a separate local python and am using it to call setup.py. I'm using py2app 0.7.3, is this not the latest version? – vik Jul 11 '13 at 16:15
  • 1
    It seems to be...can you modify setup.py to import sys and print sys.executable? And, can you try without virtualenv? – kirbyfan64sos Jul 11 '13 at 17:29

1 Answers1

1

Py2app will not include system files, such as the python installation in /System/Library/Frameworks, in your application bundle.

To create a bundle that also includes Python you need to install a separate version of Python (and all libraries that you use).

However, note that the app created with the system version of Python should work properly on machines with the same release of OSX, or a later release.

Ronald Oussoren
  • 2,715
  • 20
  • 29
  • I am using zc.buildout to set up my environment, and it seems that the local python is not a standard python. When I use py2app with it, it creates the semi-standalone app. If I make a virtualenv with a standard python however, I get the desired result. Is there a way you know of to get buildout to download/use the correct python for py2app? – vik Jul 15 '13 at 21:41
  • I don't use buildout myself. If py2app creates a semi-standalone build with it, buildout either creates a static build of python (no shared library with the python interpreter), or uses /usr/bin/python instead of the one you want to use. – Ronald Oussoren Jul 16 '13 at 06:02