On Sun, 2008-07-20 at 18:22 +0100, Martin Aspeli wrote:
Hi,
Suppose I have an interface IDerived that's derived from an interface
IBase, overriding a field from it.
from zope.interface import Interface
from zope.schema import TextLine
class IBase(Interface):
... a =
On Wed, 2008-07-16 at 07:44 -0400, Philipp von Weitershausen wrote:
Chris Withers wrote:
Hi All,
Just me, or is it excessive that we have:
http://mail.zope.org/pipermail/zope3-checkins/
This one is obsolete now.
I suggest disabling subscription for that one.
Summary of messages to the zope-tests list.
Period Mon Jul 21 11:00:00 2008 UTC to Tue Jul 22 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Mon Jul 21 21:05:07 EDT 2008
URL:
I often find that I debug problems by inserting a pdb.set_trace() in
code, and then quitting the debugger with q once I've gathered
information I need to make code changes. This causes a BdbQuit
exception to be raised and propagated to the test runner. The
resulting traceback isn't actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Log message for revision 88701:
With the new grokcore.component 1.5, we can simply say
from grokcore.component import *
and only get the actual public API imported into the local namespace.
Please
Hi Christian,
So, I'm wondering:
- Is it harmful to have two fields with the same order like this when
they share a name?
Sharing a name sounds weird. The attribute get's overriden and the
field from the base class isn't considered anymore.
Right, that's what I meant. Except that if
