Issue #59 wontfix

install problem on Snow Leopard

Anonymous created an issue

I installed Distribute on a Snow Leopard box using the default Python that comes with OS X. I used the installation method recommended in the docs, the script. Now easy_install fails no matter what package I try to install (it does not get around to looking for the name of the requested package):

$ easy_install blablabla Traceback (most recent call last): File "/usr/bin/easy_install-2.6", line 10, in <module> load_entry_point('setuptools==0.6c9', 'console_scripts', 'easy_install')() File "/Library/Python/2.6/site-packages/distribute-0.6.3-py2.6.egg/", line 281, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/Library/Python/2.6/site-packages/distribute-0.6.3-py2.6.egg/", line 2197, in load_entry_point raise ImportError("Entry point %r not found" % ((group,name),)) ImportError: Entry point ('console_scripts', 'easy_install') not found

It seems that the installation did not upgrade the "easy_install-2.6" script located in "/usr/bin". It is fixed by replacing

load_entry_point('setuptools==0.6c9', 'console_scripts', 'easy_install')()


load_entry_point('distribute==0.6.3', 'console_scripts', 'easy_install')()

Comments (5)

  1. Ian Bicking

    This seems to happen... often. Usually it's a version mismatch, not a package change, but that's because usually packages don't change (and distribute is an exception).

    It's possible that he copied a script, has another script on $PATH somewhere, somehow something changed where scripts are installed (e.g., a distutils.cfg change, or the per-user distutils config), maybe(?) that the script is not writable but other data is (I'm not sure if that's a fatal error?) or maybe that it is a fatal error but at such a late stage that everything else basically installed. Anyway, it happens a lot to all packages. Usually the best solution is to reinstall, maybe carefully checking for errors in the installation output.

    Hopefully distribute will use a less error-prone script writing technique. For this case, it is unlikely you will be able to ensure that scripts are always overwritten correctly on distribute installation; you may want to consider special casing load_entry_point.

  2. Ned Deily

    Also, IIRC, the Apple-supplied setuptools easy_install will install scripts into /usr/local/bin which is normally the right thing to do. Normally one should never install or modify anything in /usr/bin on OS X. That's Apple's territory and could very well be wiped out on an OS X update or depended on by other system components. The Apple-supplied Python breaks out its site-packages dir into /Library/Python/2.6/site-packages/ so as not to have user contamination of its framework in /System/Library/Frameworks/Python...

    BTW, other OS X Python framework builds, like the ones from or from MacPorts, will install scripts into the bin directory of the framework, i.e. /Library/Frameworks/Python.frameworks/Versions/{2|3}.x/bin or /opt/local/Library/Frameworks/Python..., respectively. Those directories may or may not be on $PATH by default. An implication is that every Python framework instance has its own bin directory and thus can and normally will have its own easy_install script.

  3. Log in to comment