New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easy_install would mess up the order of sys.path in develop install #539

Plypy opened this Issue Apr 8, 2016 · 1 comment


None yet
2 participants

Plypy commented Apr 8, 2016


Setuptools 20.6.7
Ubuntu server 14.04 within VirtualBox


Debian alike has two paths for python packages, one is for packages managed by apt /usr/lib/python*.*/dist-packages/, the other is for packages managed by pip or other 3rd-party software /usr/local/lib/python*.*/dist-packages/. Usually, the latter holds newer packages, so it's placed before the former.

After performing a python develop, I found that all projects crashed with something like ImportError. After some research, it seems to me that in develop install easy_setup would add current project's and its dependencies' paths into an easy_setup.pth file in order to modify sys.path. However if a package is located in /usr/lib/python*.*/dist-packages/, easy_setup would still add this path into easy_setup.pth, which would cause this path place prior to /usr/local/lib/python*.*/dist-packages/ and lead those disasters.

My temporary workaround is to move dependencies located in /usr/lib/python*.*/dist-packages/ to /usr/local/lib/python*.*/dist-packages/.

Hope you can fix this, it has spent me lots of time to discover where the problem is.



This comment has been minimized.


RonnyPfannschmidt commented May 9, 2016

im under the impression this is a case of a distribution breaking the worldd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment