Christian Theune wrote:
originally we intended to do a Zope 3.3.1 release in November to get
virtually bug free.
I didn't see any momentum on this. How about a bug day?
Btw: I didn't want to sound rude here to anybody who was fixing bugs in
the last time. I just wanted to express that I
What about next week? I don't care so much about the specific day.
Philipp von Weitershausen wrote:
Christian Theune wrote:
originally we intended to do a Zope 3.3.1 release in November to get
virtually bug free.
I didn't see any momentum on this. How about a bug day?
Btw: I didn't want to
Christian Theune wrote:
What about next week? I don't care so much about the specific day.
I'd be for Wednesday.
Philipp von Weitershausen wrote:
Christian Theune wrote:
originally we intended to do a Zope 3.3.1 release in November to get
virtually bug free.
I didn't see any momentum on
Hi,
Philipp von Weitershausen wrote:
Christian Theune wrote:
What about next week? I don't care so much about the specific day.
I'd be for Wednesday.
It's Wednesday November 16 then.
I've set up a search that currently contains 39 bugs with the following
search options:
Status: Accepted,
Hi again,
Christian Theune wrote:
Hi,
Philipp von Weitershausen wrote:
Christian Theune wrote:
What about next week? I don't care so much about the specific day.
I'd be for Wednesday.
It's Wednesday November 16 then.
And the price for noticing the wrong date goes to: Fred
I meant
I'm working on enhancing zope.app.apidoc, but I ran into an exception
that's hard to decipher. I've attached the traceback. I don't know
which __init__() it's complaining about, and I don't know how to find
out. What can I do to find out which __init__() the adapter hook is
trying to call?