At 07:59 PM 9/18/2010 +0300, anatoly techtonik wrote:
>On Sun, Sep 12, 2010 at 9:08 PM, P.J. Eby <pje(a)telecommunity.com> wrote:
> > That issue was fixed in October 2009, so you are likely using something
> > <0.6c11.
>I am using setuptools-0.6c11-py2.6.egg on Windows Vista.
Oops. My bad - this was actually fixed only 7 months ago, in
February 2010, and it's not in 0.6c11, only the nightly
snapshots. To update your installation, run:
easy_install -U setuptools
This should give you 0.6c12dev-r_something_or_other. ;-)
> > 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? ;-)
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), 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.)