[Pythonmac-SIG] py2app creating semi_standalone instead of standalone app

Brendan Simon (eTRIX) Brendan.Simon at eTRIX.com.au
Wed Aug 5 04:35:44 CEST 2009


Maybe it has something to do with this statement in the py2app website.

    If the --semi-standalone option is used (forced if a vendor Python
    is being used), then the not_stdlib_filter will be automatically
    added to ensure that the Python standard library is not included.


My python is 2.5.4 from Python.org.  My freind's python is python 2.5.1
(standard on Leopard from Apple).
I presume my friends python is "a vendor Python" and thus
semi-standalone is being forced.

Still not sure what the correct fix is :(


Brendan Simon (eTRIX) wrote:
> I have a wxPython app which works on my Mac.  I created an app bundle
> and this works on my Mac and my friends Mac :)
>
> All good, except that if I give my friend the source code and get him to
> create the app, the app is created as semi_standalone, and the app does
> not work as some modules cant be found.  I am assuming the problems is
> is related to the semi_standalone versus standalone, but not 100% sure.
>
> Any idea why my friend's build is semi_standalone and mine is standalone
> ??  It's the same source.
>
> Any ideas on how to make standalone explicit with py2app ??
>
> I see the --semi-standalone option in py2applet, but I don't think my
> friend should have to run pyapplet, right ???   Setup is already created.
> Hmmm, maybe I have explicitly specify standalone in setup.py somewhere ???
>
> Thanks, Brendan.
>
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Brendan_Simon.vcf
Type: text/x-vcard
Size: 267 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20090805/4cd89dd3/attachment.vcf>


More information about the Pythonmac-SIG mailing list