On Sun, Sep 19, 2010 at 2:04 AM, P.J. Eby
This should give you 0.6c12dev-r_something_or_other. ;-)
Ok. SF .egg installation from /download URL is fixed. But the logic to prefer shorter URL is not.
Note, however, that since the full source distribution *also* includes the python code, all that's needed is to change its setup.py slightly and move it to the root of the source tree.
If the Python was the only code inside - that'd be acceptable, but it seems like the proper fix lies in setuptools AI code.
You do realize that asking everybody to update their version of setuptools in order to be able to install one particular package is a little unrealistic? I mean, *your* setuptools is at least seven months out of date, so even if I changed this, how long would it be till your users updated? ;-)
1. s/everybody/package users/ 2. s/order/installation instructions/ 3. s/particular/this/ Yes. I realize that it is much easier to set setuptools requirements once that to download manually from PyPI everytime.
In truth, I do have an idea that would actually fix this problem in the Google case (a change to the way the source is processed after extraction),
For the start it will help if 'easy_install' download package from PyPI if download_url for this package is not set. I understand that fix to remove shorter URL preference logic is too complicated, so perhaps it will be easier to implement this solution.
but it will likely be a while before I can implement it, and a while further still before everyone has installed the update. (Note that 0.6c5 and 0.6c9 are still very popular versions, and 0.6c9 is like *two years* out of date.)
This won't be a problem two years later if you fix the issue today. =) -- anatoly t.