egg-info directory name lacks Python version string
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
distribute (Debian) |
Fix Released
|
Unknown
|
|||
distribute (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
For some reason, the version of distribute that ships under the python-setuptools package for Lucid and Maverick creates egg-info directories that lack the Python version string (on Lucid and Maverick, this identifier would be "py2.6"). For example, when installing the Python package yolk version 0.4.1, the egg-info directory created is named "yolk-0.
https:/
I am trying to understand why the behavior of the version of distribute that ships in the python-setuptools package is inconsistent with the upstream behavior of distribute.
More specifically, I am concerned there may have been Debian/
description: | updated |
Changed in distribute (Debian): | |
status: | Unknown → New |
Changed in distribute (Debian): | |
status: | New → Fix Released |
Pip uninstall calls the Distribution. egg_name( ) method, and appends ".egg-info", to determine where to find package metadata. This is precisely the same technique used by setuptools/ distribute' s install_egg_info command to determine the name of the metadata directory when creating it (see https:/ /bitbucket. org/tarek/ distribute/ src/f64c2d57df4 3/setuptools/ command/ install_ egg_info. py). So somehow Ubuntu's packaged version of distribute (python-setuptools) is breaking this symmetry: metadata is installed under an egg-info dir lacking pyversion, but when pip calls the Distribution. egg_name( ) method it gets a name back that includes pyversion.
This breaks pip uninstall for all users of Ubuntu's python-setuptools package. As far as I can tell there is nothing wrong with what pip is doing here; the breakage is in Ubuntu's package.