-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16.03.2009 17:40 Uhr, Hanno Schlichting wrote:
Tres Seaver wrote:
Andreas Jung wrote:
Please look at the getPackages() method taking the version*cfg files into account. So all versions should be pinned. However there is obviously a difference between using buildout with pinned versions and setuptools or a small undetected hole in the process. The issue must be that one of the "pinned" dependencies (zope.publisher?) has an unpinned dependency (maybe transitively?) which requires a newer version of zope.component.
What I think is more likely to have happened here is:
An additional package (like one under development) was installed first. This depends on some zope.foo package (maybe zope.publisher) which wants zope.component 3.6. setuptools goes and fetches the latest version of all of these. Now later on the Zope2 egg is put into the environment and requires zope.component 3.5.1 - result VersionConflict.
Not sure about this theory - I can reproduce the version mismatch with an almost plain Python 2.5 installation - especially it is reproducable within a virtualenv --no-site-package environment. On the other hand: I can not reproduce this error on my Linux box with a Python 2.4 installation with pretty large site-packages dir :->
Setuptools loads packages and puts them into the environment as it finds them. It doesn't build a full tree of dependencies first. This is what pip adds for example.
pip produces the same result. Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm+h60ACgkQCJIWIbr9KYypHACcCtI1h5fwXO9RFq1gO28J9rQr Y/4AnifSSIuNRHW6Chim7KRxOvtWZvL3 =fpxY -----END PGP SIGNATURE-----