easy_install will install a package that is already there
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-setuptools |
Unknown
|
Unknown
|
|||
python-setuptools (Ubuntu) |
Confirmed
|
High
|
Barry Warsaw | ||
Bug Description
Binary package hint: python-setuptools
Upstream bug report:
http://
This causes compatibility problems between distribute and setuptools, and shows up when using virtualenv, which uses distribute by default (as does our python-setuptools package). From distutils-sig, here's a reproducible test case for Lucid:
Sure. Create a dummy setup.py:
from setuptools import setup
setup(name="foo", install_
with "somepkg" any package already installed on ubuntu, and then:
virtualenv tmp
source tmp/bin/activate
python setup.py install
You will see that somepkg is downloaded and installed even though it
is already there. It happened for me for any value of somepkg,
including twisted, django, simplejson.
As for using setuptools instead of distribute in virtualenv, I cannot
see the option on my current machine (with lucid virtualenv), which is
weird because I clearly remember having seen it at work. I will check
there to see what's different,
Changed in python-setuptools (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Barry Warsaw (barry) |
milestone: | none → ubuntu-10.04.1 |
tags: | added: lucid |
Works for me on the current Lucid:
$ sudo easy_install extensions
Searching for extensions
...
Processing dependencies for extensions
Finished processing dependencies for extensions
$ virtualenv /tmp/test 'mindeponpywin3 2', install_ requires= ['extensions' ])
...
$ cd /tmp/test
$ more setup.py
from setuptools import setup
setup(name=
$ sudo bin/python setup.py install lib/python2. 6/dist- packages/ extensions- 0.4-py2. 6.egg
...
Using /usr/local/
...