Hi Raphael, On Fri, May 7, 2010 at 16:52, Raphael Hertzog <hert...@debian.org> wrote: > Hi, > > > On Sun, 21 Mar 2010, Carl Chenet wrote: >> I'm a new maintainer for the python-pip package and it would be great to >> solve this blocking issue. >> >> The python-pip and pip packages have quite the same popcon, and it is >> hard to select one using the name "pip". > > I think the issue has been open for long enough without clear consensus. > Hence all packages should rename their /usr/bin/pip to something else and > document the difference vs upstream in README.Debian. > > BTW, finding new names is hard, but choosing a 3 letter acronym is a > recipe for problems... > > Please take care to coordinate with other depending packages if needed > (virtualenv for python-pip?).
of course I'm s little biased on this, but I'm attending Pycon italia and 2 talks (over the 4 given by know) already provide explicit references to pip and also about how to use it (that's as simple as "pip install <module>"). I don't know how strong is the tool 'pip' into the perl world, but it's absolutely well known, used and strongly suggested (along with virtualenv) in the Python world, so diverging from its original name would be another source of frustration for the python community willing to use debian (and that community is already being harmed several times). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
