PackageNotes |
UserPreferences |
The PEAK Developers' Center | FrontPage | RecentChanges | TitleIndex | WordIndex | SiteNavigation | HelpContents |
Feel free to edit this page to add your successes and problems installing packages with EasyInstall. Please try to keep the lists in alphabetic order, for the convenience of people who are looking to see if success has already been reported for a particular package.
Note that some packages (including ones listed above) contain other information besides Python packages in their distribution files, such as documentation, scripts, sample data, etc. These other files are not installed by EasyInstall, so if you want to access them, you will need to download the distribution, and then give its filename to Easy Install to do the installation. You can then extract and use any other files you need direct from the original distribution.)
If you are responsible for any of the following packages, please consider making changes so that your downstream users can use EasyInstall to install them. If you're a user of one of these packages, please consider contributing a patch to the package's authors to make them compatible.
non-conventional layout (the setup.py file is in the base python package). Package at http://prdownloads.sourceforge.net/zpt/ZopePageTemplates-1.4.0.tgz?download -- the setup file looks like this:
from distutils.core import setup setup( name = 'ZopePageTemplates', maintainer = 'Kevin Smith', maintainer_email = 'Kevin.Smith@theMorgue.org', description = 'Zope Page Templates', extra_path = 'ZopePageTemplates', packages = ['.','TAL','ZTUtils'], )
I'm guessing the extra_path part causes problems. It gets installed with no ZopePageTemplate package, instead it's all top-level packages. Well, maybe eggs are actually doing the right thing; but I've become so used to using --install-lib=... to install packages, and the ZopePageTemplates.pth statements gets ignored in that case, that I expect it to be contained in a package even though the setup file isn't really saying to do that. Hrm.
When building with MinGW/msys on Windows, I've always found that to compile/install source Python packages with C extensions, I need to do:
python setup.py build -cmingw32 python setup.py install --skip-build
EasyInstall doesn't know that that's required, and as such, I can't put together any eggs with C extensions.
As an example, I tried to EasyInstall the up-to-the-minute PEAK tarball, and got:
Downloading c:/temp/PEAK.tar.gz Installing PEAK.tar.gz error: Setup script exited with error: Python was built with version 7.1 of Visual Studio, and extensions need to be built with the same version of the compiler, but it isn't installed.
That's the same error I get with any source C extension that I try to build with a standard setup.py install, and is the reason I need to compile in two steps as shown above
-- JayParlar