[Zope-dev] zope-tests - FAILED: 5, OK: 8

[Adam Groszer]

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.5>c:\Python33_64\python.exe setup.py install

as next I'll update c:\Python33_(32|64) to 3.3.2, because currently it's
just 3.3.0


On Wed, Jul 17, 2013 at 12:56 PM, Adam Groszer <agroszer at gmail.com> wrote:

> 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 <marius at 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:
>> > > 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 setuptools
>>    >>> setuptools.__file__
>>    '....\\setuptools-0.7.1-...'
>>
>> and works fine, while winbot's c:/python26_64/python.exe has
>>
>>    >>> import setuptools
>>    >>> setuptools.__file__
>>    '....\\distribute-0.6.44-...'
>>
>> and doesn't.
>>
>> > +1.  Let's just get past the distribute / old setuptools mess and get on
>> > with our lives.
>>
>> 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.
>>
>> IIRC there's some sort of ez_setup.py that you can run?  Never mind, I
>> can read the fine manual:
>> https://pypi.python.org/pypi/setuptools/0.9.5#windows
>>
>> So, here's what I did:
>>
>>  - rdesktop'ed into winbot
>>  - Control Panel -> Add/Remove Programs
>>  - removed Python 2.6 setuptools 0.6c11 (it said it was already removed,
>>    so I just OK'ed removing the add/remove programs item)
>>  - removed Python 2.7 setuptools 0.6c11 (this time it said it removed 18
>>    files and directories)
>>  - left setuptools 0.6c11 installers for Python 2.4 and 2.5 alone
>>    because meh
>>  - launched Git bash
>>  - cd /c/Python26_64/Lib/site-packages
>>  - rm -rf setuptools* distribute*
>>  - cd /tmp
>>  - curl https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py >
>> ez_setup.py
>>  - /c/Python26_64/python ez_setup.py
>>  - cd /c/Python27_64/Lib/site-packages
>>  - rm -rf setuptools* distribute*
>>  - cd /tmp
>>  - /c/Python27_64/python ez_setup.py
>>
>> And now I'm wondering if those control panel installers were about
>> 32-bit or 64-bit installs, and I wonder if I broke Python27_32 by
>> removing all traces of setuptools form there.  Let's check:
>>
>>    $ /c/Python27_32/python
>>    >>> import setuptools
>>    >>> setuptools.__file__
>>    '....\\distribute-0.6.44-...'
>>
>> Huh?  And no builds failed on py_270_win32?  I don't understand, and I
>> don't _want_ to understand.  Let's just see what buildbots report
>> tomorrow.
>>
>> Marius Gedminas
>> --
>> http://pov.lt/ -- Zope 3/BlueBream consulting and development
>>
>> _______________________________________________
>> Zope-Dev maillist  -  Zope-Dev at zope.org
>> https://mail.zope.org/mailman/listinfo/zope-dev
>> **  No cross posts or HTML encoding!  **
>> (Related lists -
>>  https://mail.zope.org/mailman/listinfo/zope-announce
>>  https://mail.zope.org/mailman/listinfo/zope )
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/zope-dev/attachments/20130717/72e3e458/attachment.html>