Versioned egg fragment in URLs leading to multiple installs of same package

[markmc]

In OpenStack, we hit a situation where:

pip -vvv install http://tarballs.openstack.org/oslo.config/oslo.config-1.2.0a3.tar.gz#egg=oslo.config-1.2.0a3 python-keystoneclient==0.3.1

would result in both oslo.config-1.2.0a3 and oslo.config-1.1.1 getting installed in the venv

The issue is that 1.1.1 gets in because python-keystoneclient has:

oslo.config>=1.1.1

and pip see itself as installing two distinct packages : 'oslo.config-1.2.0a3' and 'oslo.config'

Basically, we're using the entire egg fragment from the URL as the package name even though it may contain a version number

[markmc]

I hacked up some scripts to test some of stuff and here's some logs of the above test case

Firstly with 1.4rc3:

https://github.com/markmc/pip-install-debug/blob/master/results/markmc3/t3.log#L1152

Installing collected packages: oslo.config-1.2.0a3, python-keystoneclient, six, d2to1, pbr, iso8601, prettytable, requests, simplejson, oslo.config, setuptools-git

and then with my fix:

https://github.com/markmc/pip-install-debug/blob/master/results/markmc4/t3.log#L1121

Installing collected packages: oslo.config, python-keystoneclient, six, d2to1, pbr, iso8601, prettytable, requests, simplejson, setuptools-git

[dstufft]

If I recall this was able to be worked around by making it #egg=oslo.config and not #egg=oslso.config-1.2.0a3 wasn't it?

Feels like it's probably a bug caused by the . in oslo.config confusing the separation of version and name.

[markmc]

The dot in the name isn't a problem AFAICT

It used to be 'oslo-config' and we had to normalize that to 'oslo_config' in egg URL fragments

[qwcode]

closing this as dupe to #1249, so we can have one issue for this.