Chris McDonough wrote:
> I'll throw out the obvious...
>
> Why not subclass Interface in zope.component and make the required API
> additions there? If it were anybody but us thinking about doing this,
> they'd probably just subclass.
Because then, if you use third-party code that uses
zope.int
On Sun, Dec 20, 2009 at 11:12:14PM +0100, Lennart Regebro wrote:
> On Sun, Dec 20, 2009 at 17:36, Marius Gedminas wrote:
> > My app's buildbot went all red last night, because its config wants the
> > latest zope.testing (for our developers' convenience), and the latest
> > zope.testing release no
On Sun, Dec 20, 2009 at 17:36, Marius Gedminas wrote:
> My app's buildbot went all red last night, because its config wants the
> latest zope.testing (for our developers' convenience), and the latest
> zope.testing release no longer ships its own copy of doctest.py, I
> guess:
No, it's still ther
My app's buildbot went all red last night, because its config wants the
latest zope.testing (for our developers' convenience), and the latest
zope.testing release no longer ships its own copy of doctest.py, I
guess:
from zope.testing.doctestunit import DocTestSuite
ImportError: cannot import
Am 20.12.2009 um 05:52 schrieb Nikolay Kim:
> Log message for revision 106800:
> release 3.7.4
>
> Changed:
> A zope.app.security/tags/3.7.4/
> U zope.app.security/tags/3.7.4/CHANGES.txt
> U zope.app.security/tags/3.7.4/setup.py
>
> -=-
> Modified: zope.app.security/tags/3.7.4/CHANGES.t
Summary of messages to the zope-tests list.
Period Sat Dec 19 12:00:00 2009 UTC to Sun Dec 20 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Dec 19 20:37:13 EST 2009
URL: http://
