buildout picks other (outdated) setuptools version than a simple "import setuptools" in system python (Mac OS X)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
New
|
Undecided
|
Unassigned |
Bug Description
bin/buildout picks another setuptools version on my Mac OS X system than "import setuptools" in the system's /usr/bin/python. This seems unintuitive and from the conversations in the zope channel on freenode I believe this is probably a bug that should be fixed.
Basically, Mac OS X does have multiple versions of setuptools available:
/Library/
/System/
Using the system python for a short test, everything seems to be fine:
iMac01:~ jonasthiem$ python
Python 2.6.1 (r261:67515, Feb 11 2010, 00:51:29)
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import setuptools
>>> setuptools
<module 'setuptools' from '/Library/
Then using buildout, this happens:
iMac01:
/Users/
import pkg_resources
/Users/
import pkg_resources
Installing 'mr.developer', 'buildout.
We have the distribution that satisfies 'mr.developer=
We have the distribution that satisfies 'buildout.
While:
Installing.
Loading extensions.
Error: There is a version conflict.
We already have: setuptools 0.6c9
iMac01:
summary: |
buildout picks other (outdated) setuptools version than a simple "import - setuptools" in system console (Mac OS X) + setuptools" in system python (Mac OS X) |
(Please note using virtualenv, it works fine)