On Jul 17, 2013, at 12:41 , Marius Gedminas mar...@gedmin.as wrote:
I'm somewhat ashamed to admit that I don't know how to do that.
Normally I get setuptools with sudo apt-get install python-setuptools,
or by creating a virtualenv.
I have setuptools 0.9.1 deb packages if you need them. One
On Tue, Jul 16, 2013 at 07:08:39PM -0400, Tres Seaver wrote:
On 07/16/2013 06:53 AM, Marius Gedminas wrote:
Perhaps manually installing setuptools = 0.7 into c:\python2*_64
would fix the failing builds?
Further evidence for this suggestion: winbot's c:/python26_32/python.exe has
import
Hi,
Yah well just leave it. I'll try to get to it.
I'll stash a recent setuptools into all pythons.
On Wed, Jul 17, 2013 at 12:41 PM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Jul 16, 2013 at 07:08:39PM -0400, Tres Seaver wrote:
On 07/16/2013 06:53 AM, Marius Gedminas wrote:
Done.
What I did is for every python version installed there:
- clean any remnants manually of setuptools/distribute in site-packages
- get a tarball of the latest setuptools (0.9.5), untarred it
- installed setuptools from the source:
C:\install\setuptools-0.9.5c:\Python33_64\python.exe setup.py
On Tue, Jul 16, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077848.html
[2]FAILED winbot / ZODB_dev py_270_win64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/16/2013 06:53 AM, Marius Gedminas wrote:
Perhaps manually installing setuptools = 0.7 into c:\python2*_64
would fix the failing builds?
+1. Let's just get past the distribute / old setuptools mess and get on
with our lives.
Tres.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/2013 09:00 PM, Zope tests summarizer wrote:
[2]FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2013-May/074321.html
[3]FAILED winbot / ZODB_dev py_265_win64
