The PEAK Developers' Center   PackageNotes UserPreferences
 
HelpContents Search Diffs Info Edit Subscribe XML Print View
Version as of 2005-06-08 09:10:10

Clear message


EasyInstall Experience Reports

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.

Installed, Appeared OK

Installation Notes/Issues

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.

ipython-0.6.13
Appears to install correctly, but it's not clear to me if perhaps it expects users to edit the files in its IPython/UserConfig directory, or whether those are just templates.
ll-sisyphus-0.10.1
Author's name in package metadata includes an 8-bit character, which can't be written to PKG-INFO file
ModelingCore-0.9-pre-17.1
complains about cheetah-template not being found, and requires you to "Press ENTER to Continue". Apart from this, appears to install correctly. (The templates are intended to be compiled to .py files, which are then installed as part of the normal setup() process. But, it comes with pre-compiled versions of the templates, so it works fine except for the "press enter" thing.)
SpreadModule-1.5
needs Spread include files already present/installed (might work if so)
ReportLab-1.20
setup.py is in a third-level directory. Also, it tries to second-guess install locations, so even if it ran, it would require some hacking of its data file path munging code in setup.py. This would probably work fine if it were changed to use the de-facto standard hack for distutils.command.install_data, used by other packages to install data in their package directories.
Twisted-2.0.1
setup aborts, demanding that zope.interface be installed (maybe they will replace w/egg dependency in future?)
Zope-X3.0.0
no setup.py
Zope Page Templates (zpt.sf.net) 1.4

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.

Anything With MinGW (and Cygwin?)

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

PythonPowered
EditText of this page (last modified 2005-06-08 09:10:10)
FindPage by browsing, title search , text search or an index
Or try one of these actions: AttachFile, DeletePage, LikePages, LocalSiteMap, SpellCheck