If we decide to port zope.org-based projects to Python 3, please
please please, port them to Python 2&3 rather than relying on 2to3 (or
3to2). That is, update the code to work with both Python 2 and Python
3. Relying on 2to3 (or 3to2) is a headache for anyone who uses a
"develop" installation of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/30/2011 01:00 AM, Zope tests summarizer wrote:
> [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
>https://mail.zope.org/pipermail/zope-tests/2011-April/039360.html
>
>
> [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/30/2011 12:20 PM, Tres Seaver wrote:
> On 04/30/2011 01:00 AM, Zope tests summarizer wrote:
>
>> [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
>>https://mail.zope.org/pipermail/zope-tests/2011-April/039360.html
>
>
>> [2
Hi,
I'd like to apply the attached patch to zope.interface trunk to make
it more easily subclassable without having to copy and paste a chunk
of its __init__ into the subclass' __init__.
Motivating factor is: I need an Interface with a hook that gets called
after InterfaceClass.__init__ to allow
This is the summary for test reports received on the
zope-tests list between 2011-04-29 00:00:00 UTC and 2011-04-30 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/