Dear Bob; Thank you, I am now a happy camper with a real stqnd-alone py2app.
For others: To get a separate installation of Python 2.3.x under Mac OSX 10.3, I downloaded the installer for MacPython-OSX 2.3.5 from: http://homepages.cwi.nl/~jack/macpython/beta.html This installs under /Library/Frameworks, and when used to run py2app, builds a stand-alone installer. Two wrinkles to be aware of: 1) location of command-line 'python' In a plain Mac OS X 10.3 installation, the command 'python' works because the system environment variable "PATH" contains a reference to "/usr/bin", and this directory contains a symbolic link "python" that points to the python program under /System/Library/Frameworks/Python.framework. However, the Python 2.3.5 installer makes the equivalent symbolic link to the python program under '/Library/Frameworks/Python.framework", but puts the symbolic link under "/user/local/bin", which is not in the default PATH environment variable. I added a symbolic "python2.3.5" in the directory "/usr/bin, pointing to the python program under 'Library/Frameworks/Python.framework", so I can invoke this python with the command "python2.3.5". 2) Location of py2app. The installer in " py2app-0.2-py2.3-macosx10.3.zip" puts the py2app package under /Library/Python/2.3. This works for the system Python, because its site-packages directory is actually a symbolic link pointing to the directory '/Library/Python/2.3". However, the Python2.3.5 installer creates a Python whose site-packages directory is a real directory, so it will never see the py2app package. I chose to fix this by deleting the real directory, and making a symbolic link with the same name to '/Library/Python/2.3" - Read Roberts On 3/21/06 11:01 AM, "Bob Ippolito" <[EMAIL PROTECTED]> wrote: > > On Mar 21, 2006, at 9:31 AM, Read Roberts wrote: > >> I can't figure out why py2app is building a only semi-standalone >> bundle app. >> Any advice appreciated, including where to look for why the >> decision is made >> to build semi-standalone. >> >> >> I conclude that the result is semi-standalone because: >> - it fails to run if I move the system python framework out of the >> paths in >> sys.path, but otherwise works fine >> - there is nothing under <bundle app name>.app/Content/Frameworks >> >> >> Context: >> - Brand new (well old, but recently crashed and now with a new hard- >> drive) >> Mac OSX system with OSX 10.3 with all updates >> - Apple developer tools from a disk image >> 'Panther_7B85_DeveloperCD.dmg" >> - Using the Apple-installed python 2.3 in /System/Library/ >> Frameworks, no >> other Python installed > > This is why. It refuses to build a standalone bundle out of the > system framework. > > -bob > _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
