If you do this, then it should work, because the "py2app" directory was indeed cleaned when you upgraded:
rm -rf /Library/Python/2.3/macholib
rm -rf /Library/Python/2.3/altgraph
Typically bdist_mpkg installers *do* clean their target first, but in this case, it's installing to a different location entirely (py2app/macholib, py2app/altgraph, etc..), so the old targets were not removed. I didn't bother to test the upgrade scenario when cutting the release, so I didn't think to add these additional steps in the preflight script.
Future upgrades won't have this problem, as I don't see a need to move things around like this again anytime soon :)
-bob
On Dec 7, 2004, at 4:00 AM, Kaweh Kazemi wrote:
bob,
i've installed py2app-0.1.6.mpkg (i had previously 0.1.5 installed, which i didn't de-install, presuming that this will be done automatically). that's what i get:
Traceback (most recent call last): File "setup.py", line 6, in ? import py2app File "/purelib/py2app/py2app/__init__.py", line 33, in ? File "/purelib/py2app/py2app/install.py", line 15, in ? File "/purelib/py2app/py2app/command/__init__.py", line 1, in ? File "/purelib/py2app/py2app/build_app.py", line 20, in ? File "/purelib/py2app/modulegraph/find_modules.py", line 21, in ? File "/purelib/py2app/modulegraph/modulegraph.py", line 15, in ? ImportError: No module named ObjectGraph
did i miss anything?
thanks, kw.
On 07.12.2004, at 06:49, Bob Ippolito wrote:
I've rolled together a new 0.1.6 release of py2app <http://undefined.org/python/#py2app> that includes the following feature enhancements and probably a few bug fixes:
modulegraph:
- This is now a top-level package and should be cross-platformish and not at all py2app specific (if someone wants a project, integrate this into py2exe/cx_Freeze/etc.)
altgraph:
- Some common code between modulegraph and macholib was moved into altgraph (the ObjectGraph data structure, for example)
macholib:
- Lots of code in its supporting library, ptypes, was removed, rewritten and optimized for performance and simplicity.
- The API has totally been changed (I don't think anyone else uses it, so I don't feel bad about it :)
- It uses altgraph for its data structure now
- More correct algorithms for locating dylibs and frameworks based upon a thorough reading of the dyld source code
bdist_mpkg:
- Made the dependency checking more specific for better Installer compatibility
- Fixed some minor bugs
py2app:
- New "plugin" target for building loadable bundles (i.e. Interface Builder palettes). This is a crazy hack, and will never work perfectly due to the icky globalness of the Python interpreter, but works well enough in practice.
- Plugin example
- Sets a new ARGVZERO environment variable that points to the argv[0] that was passed to main(...).
- Sets a new EXECUTABLEPATH environment variable that points to the actual path of the executable that was run (which will be == to ARGVZERO most of the time)
- suboptimal PyQt support (sip and PyQt are built in really strange ways and have lots of interdependencies at the C/C++ level so whenever you use ANY sip module you use ALL sip modules)
- PyQt example
- suboptimal PyOpenGL support (PyOpenGL has a stupid way of finding its version that prevents it from being easily bundled)
- PyOpenGL example
- py2applet command line tool (performs the same function as the GUI app)
-bob
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Pyobjc-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
_______________________________________________ Pythonmac-SIG maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/pythonmac-sig
