Re: [Pythonmac-SIG] py2app, system Python, and Mac App Store
On 5/4/12 9:42 PM, Kevin Walzer wrote: I'm getting quite frustrated with the app store's brain dead auto-scan tool that doesn't see proper symlinks in the framework, and I'm getting to the point where I am going to investigate other packaging tools that don't set up a framework structure--cx_freeze and/or pyinstaller. No blame to py2app here, of course. I appreciate your advice and support. I just thought I'd follow up with an update here... I was able to successfully get an update to my app submitted to the Mac App Store after switching from py2app to cx_freeze. cx_freeze doesn't bundle a framework but just moves all the Python bits into a single executable directory, so the issues with framework symlinks are side-stepped. cx_freeze development has recently resumed after a long period of inactivity, and somewhat to my surprise, it now includes good support for OS X, including running install_name_tool to make a self-contained binary. This tool seems to be very popular among PyQt developers for deploying apps on the Mac, and it also supports Python 3. I've submitted a few patches to tweak a few things, but I was able to get my own app bundled up with just a little additional work, which I'll chalk up to learning the specifics of how this tool works. Development of cx_freeze is now based at https://bitbucket.org/anthony_tuininga/cx_freeze, though it still has a SourceForge site; not sure if this new site represents the next generation, a fork, or what. In any event, I just thought I'd mention cx_freeze as a useful tool to look at. Thanks, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
Re: [Pythonmac-SIG] py2app, system Python, and Mac App Store
On 4 May, 2012, at 0:53, Kevin Walzer wrote: My recent difficulties getting a Python app uploaded to the Mac App Store (owing to apparent issues with Apple's uploader, which seems to strip out symlinks in the embedded framework) That sucks. have prompted me to look at deploying a version of my app linked to the system Python. I've never deployed a semi-standalone app, so I'm not sure what issues to be aware of. How does backward and forward compatibility work? (I'm on Lion.) If I have any extensions that I want wrapped (currently they are in my site-packages dir in /Library/Frameworks/Python), do I need to move them? --semi-standalone without --site-packages should result in a build that doesn't access your site-packages directory (and that includes /Library/Frameworks/Python). The Apple provided bits are considered part of the stdlib for this (twisted, pyobjc, ...) because they cannot be copied into the application bundle. Apple tends to be fairly careful w.r.t. backward compatibility, but when you create a semi-standalone on Lion it will not necessarily run on Snow Leopard. On a related note, does anyone else have a Python app in the Mac App Store? I don't. Ronald smime.p7s Description: S/MIME cryptographic signature ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
Re: [Pythonmac-SIG] py2app, system Python, and Mac App Store
On 5/4/12 3:32 AM, Ronald Oussoren wrote: --semi-standalone without --site-packages should result in a build that doesn't access your site-packages directory (and that includes /Library/Frameworks/Python). The Apple provided bits are considered part of the stdlib for this (twisted, pyobjc, ...) because they cannot be copied into the application bundle. How do I make sure that binary packages from my site-packages directory are copied into (and found) in the app bundle, in lib-dyload? When I try a semi-standalone build and use the --site-packages flag, my app looks in /System/Library/Frameworks/Python.framework for the modules, and the app crashes. Poking around in the list archives, it seems that this type of configuration for py2app (semi-standalone but using some packages from the site-packages dir) is a bit delicate, though my research hasn't been comprehensive. What are the best practices here? I'm getting quite frustrated with the app store's brain dead auto-scan tool that doesn't see proper symlinks in the framework, and I'm getting to the point where I am going to investigate other packaging tools that don't set up a framework structure--cx_freeze and/or pyinstaller. No blame to py2app here, of course. I appreciate your advice and support. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
[Pythonmac-SIG] py2app, system Python, and Mac App Store
My recent difficulties getting a Python app uploaded to the Mac App Store (owing to apparent issues with Apple's uploader, which seems to strip out symlinks in the embedded framework) have prompted me to look at deploying a version of my app linked to the system Python. I've never deployed a semi-standalone app, so I'm not sure what issues to be aware of. How does backward and forward compatibility work? (I'm on Lion.) If I have any extensions that I want wrapped (currently they are in my site-packages dir in /Library/Frameworks/Python), do I need to move them? On a related note, does anyone else have a Python app in the Mac App Store? Have you encountered issues with uploads or approvals? How are you setting up py2app? My recent headaches getting the app uploaded have been a real curveball, because I have had any issues previously. Thanks in advance, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
