On Aug 18, 2008, at 22:06, Bob Ippolito wrote: > The major difference between the packages on macports and > pythonmac.org is that macports is their own distro of nearly > everything, akin to installing a copy of FreeBSD over top of Mac OS X. > pythonmac.org contains packages that are self-contained and don't have > a whole new set of libraries to install (in the cases where they do > require libraries, they link them in statically for the most part). > Theses comments are from my point of view as a developer for end users on the Mac. For my pysvn project I release kits for all the python versions * Apple python 2.3 powerpc * Apple python 2.4 intel * MacPython 2.4.x powerpc * MacPython 2.5.x powerpc and intel And in the future I intend to support: * 2.6b3 framework build * 3.0b3 framework build These are all framework builds and they are totally isolated from each other. And I release pysvn as DMG kits as well. For pysvn workbench I use the wxWidgets released DMG kits. And create a application using python module bundlebuilder. Whatever you do should point to a framework build including bundelbuilder which is installed using a Mac installer. Which is the status quo so far. Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4