| 2011-02-25 19:28:20 |
Chris Lasher |
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.4.1.egg-info" instead of "yolk-0.4.1-py2.6.egg-info". This has created issues with pip; see issue 104:
https://bitbucket.org/ianb/pip/issue/104/pip-uninstall-on-ubuntu-linux
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. |
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.4.1.egg-info" instead of "yolk-0.4.1-py2.6.egg-info". This has created issues with pip; see issue 104:
https://bitbucket.org/ianb/pip/issue/104/pip-uninstall-on-ubuntu-linux
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/Ubuntu-specific patches applied that have affected the behavior of egg-info directory naming during creation to be simply "PKGNAME-VERSION.egg-info", but that someone also forgot to apply a patch to the method pkg_resources.Distribution.egg_name(), which still provides the "PKGNAME-VERSION-py2.6.egg-info", which is the expected behavior. |
|
