<div dir="ltr">Hi,<div><br></div><div>Yah well just leave it. I'll try to get to it.</div><div>I'll stash a recent setuptools into all pythons.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 17, 2013 at 12:41 PM, Marius Gedminas <span dir="ltr"><<a href="mailto:marius@gedmin.as" target="_blank">marius@gedmin.as</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jul 16, 2013 at 07:08:39PM -0400, Tres Seaver wrote:<br>
> On 07/16/2013 06:53 AM, Marius Gedminas wrote:<br>
> > Perhaps manually installing setuptools >= 0.7 into c:\python2*_64<br>
> > would fix the failing builds?<br>
<br>
</div>Further evidence for this suggestion: winbot's c:/python26_32/python.exe has<br>
<br>
>>> import setuptools<br>
>>> setuptools.__file__<br>
'....\\setuptools-0.7.1-...'<br>
<br>
and works fine, while winbot's c:/python26_64/python.exe has<br>
<br>
>>> import setuptools<br>
>>> setuptools.__file__<br>
'....\\distribute-0.6.44-...'<br>
<br>
and doesn't.<br>
<div class="im"><br>
> +1. Let's just get past the distribute / old setuptools mess and get on<br>
> with our lives.<br>
<br>
</div>I'm somewhat ashamed to admit that I don't know how to do that.<br>
<br>
Normally I get setuptools with sudo apt-get install python-setuptools,<br>
or by creating a virtualenv.<br>
<br>
IIRC there's some sort of ez_setup.py that you can run? Never mind, I<br>
can read the fine manual: <a href="https://pypi.python.org/pypi/setuptools/0.9.5#windows" target="_blank">https://pypi.python.org/pypi/setuptools/0.9.5#windows</a><br>
<br>
So, here's what I did:<br>
<br>
- rdesktop'ed into winbot<br>
- Control Panel -> Add/Remove Programs<br>
- removed Python 2.6 setuptools 0.6c11 (it said it was already removed,<br>
so I just OK'ed removing the add/remove programs item)<br>
- removed Python 2.7 setuptools 0.6c11 (this time it said it removed 18<br>
files and directories)<br>
- left setuptools 0.6c11 installers for Python 2.4 and 2.5 alone<br>
because meh<br>
- launched Git bash<br>
- cd /c/Python26_64/Lib/site-packages<br>
- rm -rf setuptools* distribute*<br>
- cd /tmp<br>
- curl <a href="https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py" target="_blank">https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py</a> > ez_setup.py<br>
- /c/Python26_64/python ez_setup.py<br>
- cd /c/Python27_64/Lib/site-packages<br>
- rm -rf setuptools* distribute*<br>
- cd /tmp<br>
- /c/Python27_64/python ez_setup.py<br>
<br>
And now I'm wondering if those control panel installers were about<br>
32-bit or 64-bit installs, and I wonder if I broke Python27_32 by<br>
removing all traces of setuptools form there. Let's check:<br>
<br>
$ /c/Python27_32/python<br>
>>> import setuptools<br>
>>> setuptools.__file__<br>
'....\\distribute-0.6.44-...'<br>
<br>
Huh? And no builds failed on py_270_win32? I don't understand, and I<br>
don't _want_ to understand. Let's just see what buildbots report<br>
tomorrow.<br>
<div class="HOEnZb"><div class="h5"><br>
Marius Gedminas<br>
--<br>
<a href="http://pov.lt/" target="_blank">http://pov.lt/</a> -- Zope 3/BlueBream consulting and development<br>
</div></div><br>_______________________________________________<br>
Zope-Dev maillist - <a href="mailto:Zope-Dev@zope.org">Zope-Dev@zope.org</a><br>
<a href="https://mail.zope.org/mailman/listinfo/zope-dev" target="_blank">https://mail.zope.org/mailman/listinfo/zope-dev</a><br>
** No cross posts or HTML encoding! **<br>
(Related lists -<br>
<a href="https://mail.zope.org/mailman/listinfo/zope-announce" target="_blank">https://mail.zope.org/mailman/listinfo/zope-announce</a><br>
<a href="https://mail.zope.org/mailman/listinfo/zope" target="_blank">https://mail.zope.org/mailman/listinfo/zope</a> )<br>
<br></blockquote></div><br></div>